November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1018) Molecule Tests don't run on Jenkins Slaves

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-1018?page=com.atlassian.jira.plugin... ] Guilherme Baufaker Rêgo reassigned SWSQE-1018: ---------------------------------------------- Assignee: Filip Brychta > Molecule Tests don't run on Jenkins Slaves > ------------------------------------------ > > Key: SWSQE-1018 > URL: https://issues.jboss.org/browse/SWSQE-1018 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Major > > Running a simple > {code:bash} > molecule test -s olm-test > {code} > inside kiali/operator/ folder doesn't work on Jenkins slaves. > Before updating from Ansible 2.8 to Ansible 2.9: > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/test-molecule/1... > After updating to Ansible 2.9: > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/test-molecule/1... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1018) Molecule Tests don't run on Jenkins Slaves

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-1018?page=com.atlassian.jira.plugin... ] Guilherme Baufaker Rêgo commented on SWSQE-1018: ------------------------------------------------ cc [~mmahoney] > Molecule Tests don't run on Jenkins Slaves > ------------------------------------------ > > Key: SWSQE-1018 > URL: https://issues.jboss.org/browse/SWSQE-1018 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Major > > Running a simple > {code:bash} > molecule test -s olm-test > {code} > inside kiali/operator/ folder doesn't work on Jenkins slaves. > Before updating from Ansible 2.8 to Ansible 2.9: > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/test-molecule/1... > After updating to Ansible 2.9: > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/test-molecule/1... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1018) Molecule Tests don't run on Jenkins Slaves

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-1018?page=com.atlassian.jira.plugin... ] Guilherme Baufaker Rêgo updated SWSQE-1018: ------------------------------------------- Sprint: Kiali Sprint #30 > Molecule Tests don't run on Jenkins Slaves > ------------------------------------------ > > Key: SWSQE-1018 > URL: https://issues.jboss.org/browse/SWSQE-1018 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Priority: Major > > Running a simple > {code:bash} > molecule test -s olm-test > {code} > inside kiali/operator/ folder doesn't work on Jenkins slaves. > Before updating from Ansible 2.8 to Ansible 2.9: > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/test-molecule/1... > After updating to Ansible 2.9: > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/test-molecule/1... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1018) Molecule Tests don't run on Jenkins Slaves

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-1018: ---------------------------------------------- Summary: Molecule Tests don't run on Jenkins Slaves Key: SWSQE-1018 URL: https://issues.jboss.org/browse/SWSQE-1018 Project: Kiali QE Issue Type: Bug Reporter: Guilherme Baufaker Rêgo Running a simple {code:bash} molecule test -s olm-test {code} inside kiali/operator/ folder doesn't work on Jenkins slaves. Before updating from Ansible 2.8 to Ansible 2.9: https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/test-molecule/1... After updating to Ansible 2.9: https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/test-molecule/1... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-651) Refactor Kiali Performance Job

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-651?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo closed SWSQE-651. ----------------------------------------- Resolution: Done > Refactor Kiali Performance Job > ------------------------------- > > Key: SWSQE-651 > URL: https://issues.jboss.org/browse/SWSQE-651 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: performance > > Kiali Performance Job needs to be refactored to reflect changes (https://github.com/kiali/kiali-performance-testing/pull/1) and (https://github.com/kiali/kiali-performance-testing/pull/2) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-904) Go through the code smells and pick 10 most critical ones

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-904?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-904: --------------------------------------------- Assignee: (was: Guilherme Baufaker Rêgo) > Go through the code smells and pick 10 most critical ones > --------------------------------------------------------- > > Key: SWSQE-904 > URL: https://issues.jboss.org/browse/SWSQE-904 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Priority: Major > Labels: automation > > Sonar reports code smells for kiali - http://cci-stage-sonar-ui.rhev-ci-vms.eng.rdu2.redhat.com:9000/dashboard?... > We need to go through that and report the most severe ones as issues to devs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4763) interface "any" tag not working as expected

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4763?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-4763: ------------------------------------------ I have moved this to the WildFly Core project but believe this may be the correct behaviour, however it has been many many years since I looked at this code. I believe the match rules are used to define which single interface to bind to and the match rules are used to select this, I may be wrong but I don't recall us matching against multiple as in some cases that could mean multiple listener sockets are required. > interface "any" tag not working as expected > ------------------------------------------- > > Key: WFCORE-4763 > URL: https://issues.jboss.org/browse/WFCORE-4763 > Project: WildFly Core > Issue Type: Bug > Components: Management > Environment: Ubuntu 18.02 > Reporter: Yann Le Tallec > Priority: Major > > The {{<any>}} tag in the {{interface}} configuration of {{standalone.xml}} should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below. > This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected: > {code:xml} > <interfaces> > <interface name="management"> > <any> > <inet-address value="127.0.0.1"/> > </any> > </interface> > </interfaces> > {code} > But if I add another (VALID) IP address inside the any tag, I can't connect any more: > {code:xml} > <interfaces> > <interface name="management"> > <any> > <inet-address value="127.0.0.1"/> > <inet-address value="10.20.230.26"/> > </any> > </interface> > </interfaces> > {code} > With the latter configuration, {{connect}} fails with the following error: > {noformat} > >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused > {noformat} > Note: to easily reproduce the problem from the cli, starting from a fresh standalone install: > {code:bash} > connect > /interface=management:undefine-attribute(name=inet-address) > /interface=management:undefine-attribute(name=any) > /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]}) > reload > /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]}) > reload > {code} > Notes: > - 10.20.230.26 must be a reachable IP - if I use a random one I can connect normally. > - if I use {{subnet-match}} I get the same issue -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4763) interface "any" tag not working as expected

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4763?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFLY-12830 to WFCORE-4763: ------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4763 (was: WFLY-12830) Issue Type: Bug (was: Feature Request) Component/s: Management (was: Security) Affects Version/s: (was: 17.0.1.Final) > interface "any" tag not working as expected > ------------------------------------------- > > Key: WFCORE-4763 > URL: https://issues.jboss.org/browse/WFCORE-4763 > Project: WildFly Core > Issue Type: Bug > Components: Management > Environment: Ubuntu 18.02 > Reporter: Yann Le Tallec > Priority: Major > > The {{<any>}} tag in the {{interface}} configuration of {{standalone.xml}} should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below. > This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected: > {code:xml} > <interfaces> > <interface name="management"> > <any> > <inet-address value="127.0.0.1"/> > </any> > </interface> > </interfaces> > {code} > But if I add another (VALID) IP address inside the any tag, I can't connect any more: > {code:xml} > <interfaces> > <interface name="management"> > <any> > <inet-address value="127.0.0.1"/> > <inet-address value="10.20.230.26"/> > </any> > </interface> > </interfaces> > {code} > With the latter configuration, {{connect}} fails with the following error: > {noformat} > >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused > {noformat} > Note: to easily reproduce the problem from the cli, starting from a fresh standalone install: > {code:bash} > connect > /interface=management:undefine-attribute(name=inet-address) > /interface=management:undefine-attribute(name=any) > /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]}) > reload > /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]}) > reload > {code} > Notes: > - 10.20.230.26 must be a reachable IP - if I use a random one I can connect normally. > - if I use {{subnet-match}} I get the same issue -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12830) interface "any" tag not working as expected

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-12830?page=com.atlassian.jira.plugin... ] Darran Lofthouse reassigned WFLY-12830: --------------------------------------- Assignee: (was: Darran Lofthouse) > interface "any" tag not working as expected > ------------------------------------------- > > Key: WFLY-12830 > URL: https://issues.jboss.org/browse/WFLY-12830 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 17.0.1.Final > Environment: Ubuntu 18.02 > Reporter: Yann Le Tallec > Priority: Major > > The {{<any>}} tag in the {{interface}} configuration of {{standalone.xml}} should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below. > This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected: > {code:xml} > <interfaces> > <interface name="management"> > <any> > <inet-address value="127.0.0.1"/> > </any> > </interface> > </interfaces> > {code} > But if I add another (VALID) IP address inside the any tag, I can't connect any more: > {code:xml} > <interfaces> > <interface name="management"> > <any> > <inet-address value="127.0.0.1"/> > <inet-address value="10.20.230.26"/> > </any> > </interface> > </interfaces> > {code} > With the latter configuration, {{connect}} fails with the following error: > {noformat} > >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused > {noformat} > Note: to easily reproduce the problem from the cli, starting from a fresh standalone install: > {code:bash} > connect > /interface=management:undefine-attribute(name=inet-address) > /interface=management:undefine-attribute(name=any) > /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]}) > reload > /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]}) > reload > {code} > Notes: > - 10.20.230.26 must be a reachable IP - if I use a random one I can connect normally. > - if I use {{subnet-match}} I get the same issue -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12830) interface "any" tag not working as expected

by Yann Le Tallec (Jira)

[ https://issues.jboss.org/browse/WFLY-12830?page=com.atlassian.jira.plugin... ] Yann Le Tallec updated WFLY-12830: ---------------------------------- Description: The {{<any>}} tag in the {{interface}} configuration of {{standalone.xml}} should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below. This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected: {code:xml} <interfaces> <interface name="management"> <any> <inet-address value="127.0.0.1"/> </any> </interface> </interfaces> {code} But if I add another (VALID) IP address inside the any tag, I can't connect any more: {code:xml} <interfaces> <interface name="management"> <any> <inet-address value="127.0.0.1"/> <inet-address value="10.20.230.26"/> </any> </interface> </interfaces> {code} With the latter configuration, {{connect}} fails with the following error: {noformat} >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused {noformat} Note: to easily reproduce the problem from the cli, starting from a fresh standalone install: {code:bash} connect /interface=management:undefine-attribute(name=inet-address) /interface=management:undefine-attribute(name=any) /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]}) reload /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]}) reload {code} Notes: - 10.20.230.26 must be a reachable IP - if I use a random one I can connect normally. - if I use {{subnet-match}} I get the same issue was: The {{<any>}} tag in the {{interface}} configuration of {{standalone.xml}} should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below. This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected: {code:xml} <interfaces> <interface name="management"> <any> <inet-address value="127.0.0.1"/> </any> </interface> </interfaces> {code} But if I add another address inside the any tag, I can't connect any more: {code:xml} <interfaces> <interface name="management"> <any> <inet-address value="127.0.0.1"/> <inet-address value="10.20.230.26"/> </any> </interface> </interfaces> {code} With the latter configuration, {{connect}} fails with the following error: {noformat} >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused {noformat} Note: to easily reproduce the problem from the cli, starting from a fresh standalone install: {code:bash} connect /interface=management:undefine-attribute(name=inet-address) /interface=management:undefine-attribute(name=any) /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]}) reload /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]}) reload {code} Notes: - if I use 10.20.230.1 instead of 230.26 the connection works normally. - if I use {{subnet-match}} I get the same issue > interface "any" tag not working as expected > ------------------------------------------- > > Key: WFLY-12830 > URL: https://issues.jboss.org/browse/WFLY-12830 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 17.0.1.Final > Environment: Ubuntu 18.02 > Reporter: Yann Le Tallec > Assignee: Darran Lofthouse > Priority: Major > > The {{<any>}} tag in the {{interface}} configuration of {{standalone.xml}} should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below. > This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected: > {code:xml} > <interfaces> > <interface name="management"> > <any> > <inet-address value="127.0.0.1"/> > </any> > </interface> > </interfaces> > {code} > But if I add another (VALID) IP address inside the any tag, I can't connect any more: > {code:xml} > <interfaces> > <interface name="management"> > <any> > <inet-address value="127.0.0.1"/> > <inet-address value="10.20.230.26"/> > </any> > </interface> > </interfaces> > {code} > With the latter configuration, {{connect}} fails with the following error: > {noformat} > >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused > {noformat} > Note: to easily reproduce the problem from the cli, starting from a fresh standalone install: > {code:bash} > connect > /interface=management:undefine-attribute(name=inet-address) > /interface=management:undefine-attribute(name=any) > /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]}) > reload > /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]}) > reload > {code} > Notes: > - 10.20.230.26 must be a reachable IP - if I use a random one I can connect normally. > - if I use {{subnet-match}} I get the same issue -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 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 November 2019