[Red Hat JIRA] (WFCORE-5235) URL.openStream fails handshake on WildFly
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFCORE-5235?page=com.atlassian.jira.plug... ]
Jeff Mesnil reassigned WFCORE-5235:
-----------------------------------
Assignee: (was: Jeff Mesnil)
> URL.openStream fails handshake on WildFly
> -----------------------------------------
>
> Key: WFCORE-5235
> URL: https://issues.redhat.com/browse/WFCORE-5235
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Dominik Lepczyński
> Priority: Major
>
> There's a problem connecting using TLS v1.3 using JSSE (URL.openStream). Connection works on the same JDK and machine in a standalone Java program. Only when the code is executed on WildFly the server_name extension is going AWOL from ClientHello message, and the connection fails with handshake_failure. It seems to be a bug in WildFly, because it happens only when running on WildFly with the rest of the code identical.
> Tested on WildFly 20.0.0.Final and 20.0.1.Final using AdoptOpenJDK 11.0.9.1_1.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 3 months
[Red Hat JIRA] (WFCORE-5235) URL.openStream fails handshake on WildFly
by Dominik Lepczyński (Jira)
Dominik Lepczyński created WFCORE-5235:
------------------------------------------
Summary: URL.openStream fails handshake on WildFly
Key: WFCORE-5235
URL: https://issues.redhat.com/browse/WFCORE-5235
Project: WildFly Core
Issue Type: Bug
Reporter: Dominik Lepczyński
Assignee: Jeff Mesnil
There's a problem connecting using TLS v1.3 using JSSE (URL.openStream). Connection works on the same JDK and machine in a standalone Java program. Only when the code is executed on WildFly the server_name extension is going AWOL from ClientHello message, and the connection fails with handshake_failure. It seems to be a bug in WildFly, because it happens only when running on WildFly with the rest of the code identical.
Tested on WildFly 20.0.0.Final and 20.0.1.Final using AdoptOpenJDK 11.0.9.1_1.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 3 months
[Red Hat 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, Kiali Sprint #46, Kiali Sprint #47, Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51 (was: Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45, Kiali Sprint #46, Kiali Sprint #47, Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50)
> 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
(v8.13.1#813001)
3 years, 3 months
[Red Hat JIRA] (SWSQE-1202) UI Automations - Overview Filters Apply
by Hayk Hovsepyan (Jira)
[ https://issues.redhat.com/browse/SWSQE-1202?page=com.atlassian.jira.plugi... ]
Hayk Hovsepyan updated SWSQE-1202:
----------------------------------
Sprint: Kiali Sprint #44, Kiali Sprint #45, Kiali Sprint #46, Kiali Sprint #47, Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51 (was: Kiali Sprint #44, Kiali Sprint #45, Kiali Sprint #46, Kiali Sprint #47, Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50)
> UI Automations - Overview Filters Apply
> ---------------------------------------
>
> Key: SWSQE-1202
> URL: https://issues.redhat.com/browse/SWSQE-1202
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Hayk Hovsepyan
> Assignee: Sunil Kondkar
> Priority: Major
> Labels: automation
>
> Overview page contains Filter options.
> We need to automate all filter types apply and result checking.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 3 months
[Red Hat JIRA] (SWSQE-1208) UI Automations - Fix random failures
by Hayk Hovsepyan (Jira)
[ https://issues.redhat.com/browse/SWSQE-1208?page=com.atlassian.jira.plugi... ]
Hayk Hovsepyan updated SWSQE-1208:
----------------------------------
Sprint: Kiali Sprint #44, Kiali Sprint #45, Kiali Sprint #46, Kiali Sprint #47, Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51 (was: Kiali Sprint #44, Kiali Sprint #45, Kiali Sprint #46, Kiali Sprint #47, Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50)
> 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
> Priority: Major
> Labels: automation
>
> https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/run-kiali-ui-te...
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 3 months