November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-983) Bookinfo installation does not create route for productpage

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-983?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-983: ------------------------------------- What does it mean it's not reproduces consistently? Does it mean that the route for bookinfo is created only sometimes? We need the route to be created always. > Bookinfo installation does not create route for productpage > ----------------------------------------------------------- > > Key: SWSQE-983 > URL: https://issues.jboss.org/browse/SWSQE-983 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Guilherme Baufaker Rêgo > Priority: Minor > Labels: infrastructure > > The checker job is expecting bookinfo productpage to be available via route. The route is not created by bookinfo installation. We need the route to be able to check that product page is browsable. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12764) Move to Bouncy Castle 1.62

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12764?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12764: ------------------------------------ Description: We need to revert WFLY-12662 as it has problems on JDK 13 [1] but we can move forward to 1.62 which doesn't have that problem or the CVE-2019-17359 that appeared in 1.63. > Move to Bouncy Castle 1.62 > -------------------------- > > Key: WFLY-12764 > URL: https://issues.jboss.org/browse/WFLY-12764 > Project: WildFly > Issue Type: Component Upgrade > Components: Security > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > We need to revert WFLY-12662 as it has problems on JDK 13 [1] but we can move forward to 1.62 which doesn't have that problem or the CVE-2019-17359 that appeared in 1.63. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12662) Update BouncyCastle from 1.60 to 1.64

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12662?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFLY-12662. ------------------------------------- Resolution: Won't Do We can't do this, BC 1.64 doesn't work properly with JDK 13: https://github.com/bcgit/bc-java/issues/620 Fixing CVE-2019-17359 was the primary motivation for going to 1.64, but that CVE was for a problem introduced in 1.63, so WildFly's use of 1.60 meant we weren't affected. I filed a separate JIRA to move to 1.62, which doesn't have the JDK 13 problem or the CVE. Since we've already gone past 1.60 I don't see a good reason to go all the way back. > Update BouncyCastle from 1.60 to 1.64 > ------------------------------------- > > Key: WFLY-12662 > URL: https://issues.jboss.org/browse/WFLY-12662 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Major > Fix For: 19.0.0.Beta1 > > > Update BouncyCastle -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12662) Update BouncyCastle from 1.60 to 1.64

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12662?page=com.atlassian.jira.plugin... ] Brian Stansberry reopened WFLY-12662: ------------------------------------- > Update BouncyCastle from 1.60 to 1.64 > ------------------------------------- > > Key: WFLY-12662 > URL: https://issues.jboss.org/browse/WFLY-12662 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Major > Fix For: 19.0.0.Beta1 > > > Update BouncyCastle -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12764) Move to Bouncy Castle 1.62

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12764: --------------------------------------- Summary: Move to Bouncy Castle 1.62 Key: WFLY-12764 URL: https://issues.jboss.org/browse/WFLY-12764 Project: WildFly Issue Type: Component Upgrade Components: Security Reporter: Brian Stansberry Assignee: Brian Stansberry -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12763) Separate the bean-validation subsystem from the 'cdi' Galleon layer

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12763?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12763: ------------------------------------ Issue Type: Task (was: Enhancement) > Separate the bean-validation subsystem from the 'cdi' Galleon layer > ------------------------------------------------------------------- > > Key: WFLY-12763 > URL: https://issues.jboss.org/browse/WFLY-12763 > Project: WildFly > Issue Type: Task > Components: Bean Validation, Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > When we created the 'cdi' layer we included bean-validation in it to avoid the need to create a separate layer. But we're starting to have basically a layer (or more) per subsystem, plus there are a number of layers that depend on 'cdi' and don't have a logical reason to bring along b-v for their use case (e.g. WFLY-12755). So I think we should break out b-v. > Here are the current layers that depend on 'cdi': > {code} > $ git grep "layer name=\"cdi\"" > galleon-pack/src/main/resources/layers/standalone/cloud-profile/layer-spec.xml: <layer name="cdi" optional="true"/> > galleon-pack/src/main/resources/layers/standalone/ee-security/layer-spec.xml: <layer name="cdi"/> > galleon-pack/src/main/resources/layers/standalone/observability/layer-spec.xml: <layer name="cdi"/> > galleon-pack/src/main/resources/layers/standalone/open-tracing/layer-spec.xml: <layer name="cdi"/> > testsuite/test-feature-pack/src/main/resources/layers/standalone/jaxrs-server/layer-spec.xml: <layer name="cdi" optional="true"/> > {code} > For 'cloud-profile' and 'jaxrs-server' I would add b-v as a new optional dependency. I think most users who might be wanting b-v would be using one of those two, or, in the images, the 'cloud-server' descendent of 'cloud-profile', so they'll still get b-v. > People directly depending on 'cdi' or expecting to get it via 'observability' or 'open-tracing' will need to adapt their config. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12763) Separate the bean-validation subsystem from the 'cdi' Galleon layer

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12763: --------------------------------------- Summary: Separate the bean-validation subsystem from the 'cdi' Galleon layer Key: WFLY-12763 URL: https://issues.jboss.org/browse/WFLY-12763 Project: WildFly Issue Type: Enhancement Components: Bean Validation, Build System Reporter: Brian Stansberry Assignee: Brian Stansberry When we created the 'cdi' layer we included bean-validation in it to avoid the need to create a separate layer. But we're starting to have basically a layer (or more) per subsystem, plus there are a number of layers that depend on 'cdi' and don't have a logical reason to bring along b-v for their use case (e.g. WFLY-12755). So I think we should break out b-v. Here are the current layers that depend on 'cdi': {code} $ git grep "layer name=\"cdi\"" galleon-pack/src/main/resources/layers/standalone/cloud-profile/layer-spec.xml: <layer name="cdi" optional="true"/> galleon-pack/src/main/resources/layers/standalone/ee-security/layer-spec.xml: <layer name="cdi"/> galleon-pack/src/main/resources/layers/standalone/observability/layer-spec.xml: <layer name="cdi"/> galleon-pack/src/main/resources/layers/standalone/open-tracing/layer-spec.xml: <layer name="cdi"/> testsuite/test-feature-pack/src/main/resources/layers/standalone/jaxrs-server/layer-spec.xml: <layer name="cdi" optional="true"/> {code} For 'cloud-profile' and 'jaxrs-server' I would add b-v as a new optional dependency. I think most users who might be wanting b-v would be using one of those two, or, in the images, the 'cloud-server' descendent of 'cloud-profile', so they'll still get b-v. People directly depending on 'cdi' or expecting to get it via 'observability' or 'open-tracing' will need to adapt their config. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12762) Upgrade wildfly-transaction-client to 1.1.8.Final

by Tomasz Adamski (Jira)

Tomasz Adamski created WFLY-12762: ------------------------------------- Summary: Upgrade wildfly-transaction-client to 1.1.8.Final Key: WFLY-12762 URL: https://issues.jboss.org/browse/WFLY-12762 Project: WildFly Issue Type: Component Upgrade Components: EJB, Transactions Reporter: Tomasz Adamski Assignee: Tomasz Adamski -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12761) Upgrade jberet from 1.3.4.Final to 1.3.5.Final

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFLY-12761?page=com.atlassian.jira.plugin... ] Ilia Vassilev updated WFLY-12761: --------------------------------- Description: https://github.com/jberet/jsr352/tree/1.3.x > Upgrade jberet from 1.3.4.Final to 1.3.5.Final > ---------------------------------------------- > > Key: WFLY-12761 > URL: https://issues.jboss.org/browse/WFLY-12761 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Affects Versions: 18.0.0.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > Labels: downstream_dependency > > https://github.com/jberet/jsr352/tree/1.3.x -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12760) Recurring failures in org.jboss.as.test.integration.ws.wsse.trust with JDK 13

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12760?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-12760: --------------------------------------- Assignee: Brian Stansberry (was: Jim Ma) > Recurring failures in org.jboss.as.test.integration.ws.wsse.trust with JDK 13 > ----------------------------------------------------------------------------- > > Key: WFLY-12760 > URL: https://issues.jboss.org/browse/WFLY-12760 > Project: WildFly > Issue Type: Bug > Components: Web Services > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > Starting on October 17 we started seeing repeated failures of 4 ws tests in the JDK 13 test job: > https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk13 > Looking at the changelog from the first day it started failing[1] one thing that stands out is it included the WFLY-12678 upgrade. > Hmm, it also included WFLY-12662, a Bouncy Castle upgrade and one of the test failures has some BC related errors in the log. > [1] https://ci.wildfly.org/viewLog.html?buildId=172054&buildTypeId=WF_MasterL... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2019