[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 (was: Kiali Sprint #39, Kiali Sprint #40)
> 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)
4 years, 7 months
[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 (was: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40)
> 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)
4 years, 7 months