August 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13803) Upgrade RESTEasy to 3.13.0.Final

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-13803?page=com.atlassian.jira.plugi... ] Ronald Sigal updated WFLY-13803: -------------------------------- Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Beta1) (was: 20.0.0.Final) > Upgrade RESTEasy to 3.13.0.Final > -------------------------------- > > Key: WFLY-13803 > URL: https://issues.redhat.com/browse/WFLY-13803 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Ronald Sigal > Assignee: Ronald Sigal > Priority: Major > Labels: downstream_dependency > Fix For: 21.0.0.Beta1 > > > Upgrade from 3.11.2.Final to 3.12.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13803) Upgrade RESTEasy to 3.13.0.Final

by Ronald Sigal (Jira)

Ronald Sigal created WFLY-13803: ----------------------------------- Summary: Upgrade RESTEasy to 3.13.0.Final Key: WFLY-13803 URL: https://issues.redhat.com/browse/WFLY-13803 Project: WildFly Issue Type: Component Upgrade Components: REST Reporter: Ronald Sigal Assignee: Ronald Sigal Fix For: 20.0.0.Beta1, 20.0.0.Final Upgrade from 3.11.2.Final to 3.12.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5104) remoting subsystem's http-connector is missing capability reference

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5104?page=com.atlassian.jira.plug... ] Brian Stansberry moved WFLY-12356 to WFCORE-5104: ------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-5104 (was: WFLY-12356) Component/s: Remoting (was: Remoting) Affects Version/s: (was: 17.0.1.Final) > remoting subsystem's http-connector is missing capability reference > ------------------------------------------------------------------- > > Key: WFCORE-5104 > URL: https://issues.redhat.com/browse/WFCORE-5104 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Reporter: Radoslav Husar > Assignee: Ranabir Chakraborty > Priority: Major > Labels: ux > > http-remoting-connector is missing capability reference to the undertow connector. > {noformat} > [standalone@localhost:9990 /] /subsystem=remoting/http-connector=http-remoting-connector:write-attribute(name=connector-ref,value=foo) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {noformat} > results in a cryptic error > {noformat} > 11:33:01,792 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service org.wildfly.clustering.cache.registry-entry.ejb.client-mappings, service org.wildfly.ejb.remote] > WFLYCTL0448: 5 additional services are down due to their dependencies being missing or failed > 11:33:15,334 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183: Service status report > WFLYCTL0185: Newly corrected services: > service jboss.ejb.association (new available) > service jboss.ejb.remoting.connector.client-mappings (new available) > service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (no longer required) > service org.wildfly.clustering.cache.registry-entry.ejb.client-mappings (new available) > service org.wildfly.clustering.cache.registry-factory.ejb.client-mappings (new available) > service org.wildfly.clustering.group.ejb (new available) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12356) remoting subsystem's http-connector is missing capability reference

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12356?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-12356: ----------------------------------------- I'm going to move this to WFCORE as that's where the remoting subsystem is. > remoting subsystem's http-connector is missing capability reference > ------------------------------------------------------------------- > > Key: WFLY-12356 > URL: https://issues.redhat.com/browse/WFLY-12356 > Project: WildFly > Issue Type: Bug > Components: Remoting > Affects Versions: 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Ranabir Chakraborty > Priority: Major > Labels: ux > > http-remoting-connector is missing capability reference to the undertow connector. > {noformat} > [standalone@localhost:9990 /] /subsystem=remoting/http-connector=http-remoting-connector:write-attribute(name=connector-ref,value=foo) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {noformat} > results in a cryptic error > {noformat} > 11:33:01,792 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service org.wildfly.clustering.cache.registry-entry.ejb.client-mappings, service org.wildfly.ejb.remote] > WFLYCTL0448: 5 additional services are down due to their dependencies being missing or failed > 11:33:15,334 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183: Service status report > WFLYCTL0185: Newly corrected services: > service jboss.ejb.association (new available) > service jboss.ejb.remoting.connector.client-mappings (new available) > service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (no longer required) > service org.wildfly.clustering.cache.registry-entry.ejb.client-mappings (new available) > service org.wildfly.clustering.cache.registry-factory.ejb.client-mappings (new available) > service org.wildfly.clustering.group.ejb (new available) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5103) Adding non existent and not required keystore fails

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-5103?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-5103: ------------------------------------- Fix Version/s: 13.0.0.Beta6 > Adding non existent and not required keystore fails > --------------------------------------------------- > > Key: WFCORE-5103 > URL: https://issues.redhat.com/browse/WFCORE-5103 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Jean Francois Denise > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 13.0.0.Beta6 > > > We are in a case where a CLI script is executed in an embedded server. They keystore added doesn't exist locally when the script is run. The operation is: > /subsystem=elytron/key-store=keystore:add(required=false, path="/etc/foo/keystore.jks", credential-reference=\{clear-text=${keystore.password}}) > Error: > "failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.keystore" => "WFLYELY00004: Unable to start the service. > [ERROR] Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYELY00022: KeyStore file '/etc/wf-secrets/keystore.jks' does not exist and required."}}, -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5103) Adding non existent and not required keystore fails

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-5103?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-5103: ------------------------------------- Priority: Blocker (was: Critical) > Adding non existent and not required keystore fails > --------------------------------------------------- > > Key: WFCORE-5103 > URL: https://issues.redhat.com/browse/WFCORE-5103 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Jean Francois Denise > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 13.0.0.Beta6 > > > We are in a case where a CLI script is executed in an embedded server. They keystore added doesn't exist locally when the script is run. The operation is: > /subsystem=elytron/key-store=keystore:add(required=false, path="/etc/foo/keystore.jks", credential-reference=\{clear-text=${keystore.password}}) > Error: > "failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.keystore" => "WFLYELY00004: Unable to start the service. > [ERROR] Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYELY00022: KeyStore file '/etc/wf-secrets/keystore.jks' does not exist and required."}}, -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5103) Adding non existent and not required keystore fails

by Jean Francois Denise (Jira)

Jean Francois Denise created WFCORE-5103: -------------------------------------------- Summary: Adding non existent and not required keystore fails Key: WFCORE-5103 URL: https://issues.redhat.com/browse/WFCORE-5103 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Jean Francois Denise Assignee: Darran Lofthouse We are in a case where a CLI script is executed in an embedded server. They keystore added doesn't exist locally when the script is run. The operation is: /subsystem=elytron/key-store=keystore:add(required=false, path="/etc/foo/keystore.jks", credential-reference=\{clear-text=${keystore.password}}) Error: "failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.keystore" => "WFLYELY00004: Unable to start the service. [ERROR] Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYELY00022: KeyStore file '/etc/wf-secrets/keystore.jks' does not exist and required."}}, -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1208) UI Automations - Fix random failures

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1208: ------------------------------------- Summary: UI Automations - Fix random failures Key: SWSQE-1208 URL: https://issues.redhat.com/browse/SWSQE-1208 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/run-kiali-ui-te... -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13759) Intermittent failure in ManagedExecutorServiceMetricsTestCase.testManagedExecutorServiceManagement

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13759?page=com.atlassian.jira.plugi... ] Cheng Fang updated WFLY-13759: ------------------------------ Description: According to [https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=...] in the last month there have been 9 failures of ManagedExecutorServiceMetricsTestCase.testManagedExecutorServiceManagement with this failure: {code:java} java.lang.AssertionError at deployment.arquillian-service//org.junit.Assert.fail(Assert.java:86) at deployment.arquillian-service//org.junit.Assert.assertTrue(Assert.java:41) at deployment.arquillian-service//org.junit.Assert.assertTrue(Assert.java:52) at deployment.ManagedExecutorServiceMetricsTestCase.jar//org.jboss.as.test.integration.ee.concurrent.ManagedExecutorServiceMetricsTestCase.testRuntimeStats(ManagedExecutorServiceMetricsTestCase.java:238) at deployment.ManagedExecutorServiceMetricsTestCase.jar//org.jboss.as.test.integration.ee.concurrent.ManagedExecutorServiceMetricsTestCase.testManagedExecutorServiceManagement(ManagedExecutorServiceMetricsTestCase.java:108) {code} First failure was reported against [https://github.com/wildfly/wildfly/pull/13414] but that was a docs only change so not relevant. It occurred on July 17 but there weren't any merge commits to master in the period between Jul 12 and Jul 20 so any change in master causing this isn't obvious. The failure is because the test checks that the # of active threads is 0 immediately after it does some activity, so it may just be a timing issue that's always been possible and just started happening recently for env reason on ci.wildfly.org. A general comment is this test would be better if its asserts reported more info about what it read from the server. Use assertEquals and report the expected and wrong value. was: According to https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... in the last month there have been 5 failures of ManagedExecutorServiceMetricsTestCase.testManagedExecutorServiceManagement with this failure: {code} java.lang.AssertionError at deployment.arquillian-service//org.junit.Assert.fail(Assert.java:86) at deployment.arquillian-service//org.junit.Assert.assertTrue(Assert.java:41) at deployment.arquillian-service//org.junit.Assert.assertTrue(Assert.java:52) at deployment.ManagedExecutorServiceMetricsTestCase.jar//org.jboss.as.test.integration.ee.concurrent.ManagedExecutorServiceMetricsTestCase.testRuntimeStats(ManagedExecutorServiceMetricsTestCase.java:238) at deployment.ManagedExecutorServiceMetricsTestCase.jar//org.jboss.as.test.integration.ee.concurrent.ManagedExecutorServiceMetricsTestCase.testManagedExecutorServiceManagement(ManagedExecutorServiceMetricsTestCase.java:108) {code} First failure was reported against https://github.com/wildfly/wildfly/pull/13414 but that was a docs only change so not relevant. It occurred on July 17 but there weren't any merge commits to master in the period between Jul 12 and Jul 20 so any change in master causing this isn't obvious. The failure is because the test checks that the # of active threads is 0 immediately after it does some activity, so it may just be a timing issue that's always been possible and just started happening recently for env reason on ci.wildfly.org. A general comment is this test would be better if its asserts reported more info about what it read from the server. Use assertEquals and report the expected and wrong value. > Intermittent failure in ManagedExecutorServiceMetricsTestCase.testManagedExecutorServiceManagement > --------------------------------------------------------------------------------------------------- > > Key: WFLY-13759 > URL: https://issues.redhat.com/browse/WFLY-13759 > Project: WildFly > Issue Type: Bug > Components: Concurrency Utilities > Reporter: Brian Stansberry > Assignee: Eduardo Martins > Priority: Minor > > According to [https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=...] in the last month there have been 9 failures of ManagedExecutorServiceMetricsTestCase.testManagedExecutorServiceManagement with this failure: > {code:java} > java.lang.AssertionError > at deployment.arquillian-service//org.junit.Assert.fail(Assert.java:86) > at deployment.arquillian-service//org.junit.Assert.assertTrue(Assert.java:41) > at deployment.arquillian-service//org.junit.Assert.assertTrue(Assert.java:52) > at deployment.ManagedExecutorServiceMetricsTestCase.jar//org.jboss.as.test.integration.ee.concurrent.ManagedExecutorServiceMetricsTestCase.testRuntimeStats(ManagedExecutorServiceMetricsTestCase.java:238) > at deployment.ManagedExecutorServiceMetricsTestCase.jar//org.jboss.as.test.integration.ee.concurrent.ManagedExecutorServiceMetricsTestCase.testManagedExecutorServiceManagement(ManagedExecutorServiceMetricsTestCase.java:108) > {code} > First failure was reported against [https://github.com/wildfly/wildfly/pull/13414] but that was a docs only change so not relevant. It occurred on July 17 but there weren't any merge commits to master in the period between Jul 12 and Jul 20 so any change in master causing this isn't obvious. > The failure is because the test checks that the # of active threads is 0 immediately after it does some activity, so it may just be a timing issue that's always been possible and just started happening recently for env reason on ci.wildfly.org. > A general comment is this test would be better if its asserts reported more info about what it read from the server. Use assertEquals and report the expected and wrong value. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1207) UI Automations - Fix failure tests because of filter

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1207: ------------------------------------- Summary: UI Automations - Fix failure tests because of filter Key: SWSQE-1207 URL: https://issues.redhat.com/browse/SWSQE-1207 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan kiali_qe.tests.test_services_page.test_filter_service_by_or_label kiali_qe.tests.test_services_page.test_filter_service_by_and_label kiali_qe.tests.test_applications_page.test_filter_applications_by_and_label -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2020