[JBoss JIRA] (SWSQE-1143) Solve python2 vs. python3 problem on jenkins slaves
by Hayk Hovsepyan (Jira)
[ https://issues.redhat.com/browse/SWSQE-1143?page=com.atlassian.jira.plugi... ]
Hayk Hovsepyan updated SWSQE-1143:
----------------------------------
Sprint: Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45 (was: Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44)
> Solve python2 vs. python3 problem on jenkins slaves
> ---------------------------------------------------
>
> Key: SWSQE-1143
> URL: https://issues.redhat.com/browse/SWSQE-1143
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
> Usage of python2 as a default python version on our jenkins slaves causes lot of troubles. It would be good to use python3 everywhere.
> e.g. lot of problem2 with openstack client on python2:
> /usr/lib/python2.7/site-packages/pkg_resources/py2_warn.py:21: UserWarning: Setuptools will stop working on Python 2
> ************************************************************
> You are running Setuptools on Python 2, which is no longer
> supported and
> >>> SETUPTOOLS WILL STOP WORKING <<<
> in a subsequent release (no sooner than 2020-04-20).
> Please ensure you are installing
> Setuptools using pip 9.x or later or pin to `setuptools<45`
> in your environment.
> If you have done those things and are still encountering
> this message, please follow up at
> https://bit.ly/setuptools-py2-warning.
> ************************************************************
> sys.version_info < (3,) and warnings.warn(pre + "*" * 60 + msg + "*" * 60)
> Traceback (most recent call last):
> File "/usr/bin/openstack", line 5, in <module>
> from openstackclient.shell import main
> File "/usr/lib/python2.7/site-packages/openstackclient/shell.py", line 24, in <module>
> from osc_lib import shell
> File "/usr/lib/python2.7/site-packages/osc_lib/shell.py", line 33, in <module>
> from osc_lib.cli import client_config as cloud_config
> File "/usr/lib/python2.7/site-packages/osc_lib/cli/client_config.py", line 18, in <module>
> from openstack.config import exceptions as sdk_exceptions
> File "/usr/lib/python2.7/site-packages/openstack/__init__.py", line 16, in <module>
> import openstack.config
> File "/usr/lib/python2.7/site-packages/openstack/config/__init__.py", line 17, in <module>
> from openstack.config.loader import OpenStackConfig # noqa
> File "/usr/lib/python2.7/site-packages/openstack/config/loader.py", line 33, in <module>
> from openstack.config import cloud_region
> File "/usr/lib/python2.7/site-packages/openstack/config/cloud_region.py", line 44, in <module>
> from openstack import proxy
> File "/usr/lib/python2.7/site-packages/openstack/proxy.py", line 24, in <module>
> from openstack import resource
> File "/usr/lib/python2.7/site-packages/openstack/resource.py", line 49, in <module>
> from openstack import utils
> File "/usr/lib/python2.7/site-packages/openstack/utils.py", line 13, in <module>
> import queue
> ImportError: No module named queue
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (SWSQE-1077) Kiali Test For Istio.io
by Hayk Hovsepyan (Jira)
[ https://issues.redhat.com/browse/SWSQE-1077?page=com.atlassian.jira.plugi... ]
Hayk Hovsepyan updated SWSQE-1077:
----------------------------------
Sprint: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45 (was: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44)
> Kiali Test For Istio.io
> -----------------------
>
> Key: SWSQE-1077
> URL: https://issues.redhat.com/browse/SWSQE-1077
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matthew Mahoney
> Priority: Major
> Labels: infrastructure
>
> The Istio.io team is requesting a Kiali test case that can be run on each submitted PR. The purpose of this test case is to validate that Kiali is not broken upon a PR submittal.
> Meeting with [~brian.avery] [~gbaufake]:
> 1) BrianA to port existing Kiali test case that was developed in old Istio.io test framework to new istiso.io framework
> https://github.com/istio/istio/blob/master/tests/e2e/tests/kiali/kiali_te...
> 2) Kiali team then to add an api test case(s) via 'curl' to validate the Istio/Kiali integration is properly functioning.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (SWSQE-1089) Remove hardcoded waiting for webhook "smcp.validation.maistra.io"
by Hayk Hovsepyan (Jira)
[ https://issues.redhat.com/browse/SWSQE-1089?page=com.atlassian.jira.plugi... ]
Hayk Hovsepyan updated SWSQE-1089:
----------------------------------
Sprint: Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45 (was: Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44)
> Remove hardcoded waiting for webhook "smcp.validation.maistra.io"
> -----------------------------------------------------------------
>
> Key: SWSQE-1089
> URL: https://issues.redhat.com/browse/SWSQE-1089
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Optional
> Labels: infrastructure
>
> https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/blob/ma...
> There is no need to wait that long. We need some dynamic check.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (SWSQE-1056) Try OCP 4.6 on IPv6 in PSI
by Hayk Hovsepyan (Jira)
[ https://issues.redhat.com/browse/SWSQE-1056?page=com.atlassian.jira.plugi... ]
Hayk Hovsepyan updated SWSQE-1056:
----------------------------------
Sprint: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45 (was: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44)
> Try OCP 4.6 on IPv6 in PSI
> --------------------------
>
> Key: SWSQE-1056
> URL: https://issues.redhat.com/browse/SWSQE-1056
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (WFLY-13763) WS-Sec Regression with WFLY18+ following upgrade to SAAJ 1.4
by Andreas Weise (Jira)
[ https://issues.redhat.com/browse/WFLY-13763?page=com.atlassian.jira.plugi... ]
Andreas Weise commented on WFLY-13763:
--------------------------------------
Good to see, that there is an idea of how to fix it. do you think it can be fixed in WFLY21 ?
> WS-Sec Regression with WFLY18+ following upgrade to SAAJ 1.4
> ------------------------------------------------------------
>
> Key: WFLY-13763
> URL: https://issues.redhat.com/browse/WFLY-13763
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Reporter: Brian Stansberry
> Assignee: Jim Ma
> Priority: Major
>
> This was reported by Andreas Weise at https://groups.google.com/g/wildfly/c/B4Gk4ljbrqE:
> After upgrading to WFY20 we are facing a regression regarding WS-Security that was introduced with Upgrade of com.sun.xml.messaging.saaj:saaj-impl in https://issues.redhat.com/browse/WFLY-12442 with WFLY18. When downgrading com.sun.xml.messaging.saaj:saaj-impl to 1.3.x the regression is fixed also in WFLY18+. We did not locate the root cause in saaj-impl 1.4+.
> The Bug was spotted within our signing algorithm used for our SOAP Web Services (which uses javax.xml.crypto.dsig Packages).
> The Bug can be reproduced easily via https://github.com/weand/wildfly-xml-sig-reproducer, which contains the most basic reproducer code of our scenario:
> Reproducer contains a Web Service implementation which uses XML Signature and more specifically the enveloped-signature transform algorithm (https://www.w3.org/TR/xmldsig-core1/#sec-EnvelopedSignature). This standard transform algorithm basically removes the whole Signature element from the digest calculation. And thats not stable since WFLY18 as the Signature element is not removed anymore! The repo also contains an arquillian test testing the SOAP webservice response using rest-assured.
> Run good scenario: Test on WFLY17
> 1) mvn clean install -Pwfly17
> 2) Test passes
> 3) see proper 'Pre-digested input' as DEBUG output of org.apache.jcp Logger (here I pretty formatted the XML):
> {code}
> 17:58:04,494 DEBUG [org.apache.jcp.xml.dsig.internal.DigesterOutputStream] (default task-1) Pre-digested input:
> 17:58:04,494 DEBUG [org.apache.jcp.xml.dsig.internal.DigesterOutputStream] (default task-1) <soap:Body xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" ID="Body">
> <ns1:echoResponse
> xmlns:ns1="http://reproducer.sig.xml.wildfly.weand.github.com/">
> <return>hello test</return>
> </ns1:echoResponse>
> </soap:Body>
> 17:58:04,495 DEBUG [org.apache.jcp.xml.dsig.internal.dom.DOMReference] (default task-1) Reference object uri = #Body
> 17:58:04,495 DEBUG [org.apache.jcp.xml.dsig.internal.dom.DOMReference] (default task-1) Reference digesting completed
> {code}
> Run failing scenario: Test on WFLY18+
> 1) mvn clean install (which defaults to 20.0.1.Final)
> 2) Test fails
> {code}
> [ERROR] testService(com.github.weand.wildfly.xml.sig.reproducer.test.XmlSignatureIT) Time elapsed: 0.874 s <<< FAILURE!
> java.lang.AssertionError:
> Expected: Expected text value '0FCBFaURtUN+0kxupRbO3pp93rPY+9d1bf7ffAw77lQ=' but was 'A+XljxuKgY2Va+YDk/Ho66i/+JQLeA9QoTH8kap7Zdk=' - comparing <DigestValue ...>0FCBFaURtUN+0kxupRbO3pp93rPY+9d1bf7ffAw77lQ=</DigestValue> at /Envelope[1]/Body[1]/Signature[1]/SignedInfo[1]/Reference[1]/DigestValue[1]/text()[1] to <DigestValue ...>A+XljxuKgY2Va+YDk/Ho66i/+JQLeA9QoTH8kap7Zdk=</DigestValue> at /Envelope[1]/Body[1]/Signature[1]/SignedInfo[1]/Reference[1]/DigestValue[1]/text()[1]:
> <DigestValue xmlns="http://www.w3.org/2000/09/xmldsig#">0FCBFaURtUN+0kxupRbO3pp93rPY+9d1bf7ffAw77lQ=</DigestValue>
> but: result was:
> <DigestValue xmlns="http://www.w3.org/2000/09/xmldsig#">A+XljxuKgY2Va+YDk/Ho66i/+JQLeA9QoTH8kap7Zdk=</DigestValue>
> at com.github.weand.wildfly.xml.sig.reproducer.test.XmlSignatureIT.testService(XmlSignatureIT.java:71)
> {code}
> 3) see invalid 'Pre-digested input' as DEBUG output of org.apache.jcp Logger:
> {code}
> 18:03:42,888 DEBUG [org.apache.jcp.xml.dsig.internal.DigesterOutputStream] (default task-1) Pre-digested input:
> 18:03:42,888 DEBUG [org.apache.jcp.xml.dsig.internal.DigesterOutputStream] (default task-1) <soap:Body xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" ID="Body">
> <ns1:echoResponse
> xmlns:ns1="http://reproducer.sig.xml.wildfly.weand.github.com/">
> <return>hello test</return>
> </ns1:echoResponse>
> <Signature
> xmlns="http://www.w3.org/2000/09/xmldsig#">
> <SignedInfo>
> <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></CanonicalizationMethod>
> <SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"></SignatureMethod>
> <Reference URI="#Body">
> <Transforms>
> <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"></Transform>
> </Transforms>
> <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"></DigestMethod>
> <DigestValue></DigestValue>
> </Reference>
> </SignedInfo>
> <SignatureValue></SignatureValue>
> </Signature>
> </soap:Body>
> 18:03:42,888 DEBUG [org.apache.jcp.xml.dsig.internal.dom.DOMReference] (default task-1) Reference object uri = #Body
> 18:03:42,888 DEBUG [org.apache.jcp.xml.dsig.internal.dom.DOMReference] (default task-1) Reference digesting completed
> {code}
> Again the digest with enveloped-signature transform algorithm works properly when downgrading saaj-impl to 1.3.x in WFLY18+.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (WFCORE-5111) Upgrade JBoss MSC from 1.4.11 to 1.4.12
by Richard Opalka (Jira)
Richard Opalka created WFCORE-5111:
--------------------------------------
Summary: Upgrade JBoss MSC from 1.4.11 to 1.4.12
Key: WFCORE-5111
URL: https://issues.redhat.com/browse/WFCORE-5111
Project: WildFly Core
Issue Type: Component Upgrade
Components: Server
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: 13.0.0.Beta6
Brings in:
Fixes:
MSC-252 Removing double word of service in the thrown exception ServiceNotFoundException
Enhancements:
MSC-255 Deprecating StabilityMonitor & StabilityStatistics
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month