January 2021 - jboss-jira - Jboss List Archives

[Red Hat 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, Kiali Sprint #46, Kiali Sprint #47, Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51, Kiali Sprint #52 (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 Sprint #45, Kiali Sprint #46, Kiali Sprint #47, Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51) > 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 (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1259) Update cachet plugin when the semaphor is migrated

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1259?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1259: ---------------------------------- Sprint: Kiali Sprint #51, Kiali Sprint #52 (was: Kiali Sprint #51) > Update cachet plugin when the semaphor is migrated > -------------------------------------------------- > > Key: SWSQE-1259 > URL: https://issues.redhat.com/browse/SWSQE-1259 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > Semaphore is being migrated to statuspage.io > We need to update our cachet plugin when it's done. > ticket: https://projects.engineering.redhat.com/browse/CCITINIT-38 -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1242) Update auto clusters to OCP 4.6

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1242?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1242: ---------------------------------- Sprint: Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51, Kiali Sprint #52 (was: Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51) > Update auto clusters to OCP 4.6 > ------------------------------- > > Key: SWSQE-1242 > URL: https://issues.redhat.com/browse/SWSQE-1242 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We need to update our auto1 and auto2 clusters to OCP 4.6. To do this, we need nightly maistra builds with new format. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1171) Create automated cleaning of old OCP clusters

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1171?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1171: ---------------------------------- Sprint: Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51, Kiali Sprint #52 (was: Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51) > Create automated cleaning of old OCP clusters > --------------------------------------------- > > Key: SWSQE-1171 > URL: https://issues.redhat.com/browse/SWSQE-1171 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Leonardo Ieggli > Priority: Major > Labels: infrastructure > > We need some cleaning mechanism for old OCP clusters. Probably to have some list of long living clusters and remove all other clusters after e.g. 1 week. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1234) Upgrade go and operator sdk versions on kiali-build jenkins worker

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1234?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1234: ---------------------------------- Sprint: Kiali Sprint #47, Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51, Kiali Sprint #52 (was: Kiali Sprint #47, Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51) > Upgrade go and operator sdk versions on kiali-build jenkins worker > ------------------------------------------------------------------ > > Key: SWSQE-1234 > URL: https://issues.redhat.com/browse/SWSQE-1234 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > To be able to update operator sdk we need to wait for https://github.com/kiali/kiali/issues/2983 -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1182) DropDown - Optimization of hierarchy.

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1182?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1182: ---------------------------------- Sprint: 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, Kiali Sprint #52 (was: 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) > DropDown - Optimization of hierarchy. > ------------------------------------- > > Key: SWSQE-1182 > URL: https://issues.redhat.com/browse/SWSQE-1182 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Currently there is a big hierarchy of DropDown objects. > It needs to be optimized. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[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, Kiali Sprint #52 (was: Kiali Sprint #44, Kiali Sprint #45, Kiali Sprint #46, Kiali Sprint #47, Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51) > 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)

5 years, 2 months

1
0
0 / 0

[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, Kiali Sprint #52 (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, Kiali Sprint #51) > 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)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery

by Adriano Teixeira de Souza (Jira)

[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ] Adriano Teixeira de Souza commented on WFLY-14284: -------------------------------------------------- Hi [~ochaloup] I have some questions to take some decisions about our production environment: 1 - According to what you say, probably this kind of errors won't occur anymore. Can I think in this way? 2 - Will it be safe to delete data / ejb-txn-recovery and data / tx-object-store if this problems occurs again? 3 - Is it safe to put a load balance like haproxy between wildfly remote outbound communication and the target server? 4 - On our tests we notice wildfly 18.0.1 has shown a fewer errors cases than wildfly 20.0.1. I wonder if could be just randomly situation or the version 18.0.1 is more stable than 20.0.1? We ar in doubt on wich to use definitely on our production environment. Could you give us some advice about it? > WildFly doesn't stop while waiting for PeriodicRecovery > ------------------------------------------------------- > > Key: WFLY-14284 > URL: https://issues.redhat.com/browse/WFLY-14284 > Project: WildFly > Issue Type: Bug > Components: EJB, Transactions > Affects Versions: 18.0.1.Final, 20.0.1.Final > Reporter: Adriano Teixeira de Souza > Assignee: Michael Musgrove > Priority: Major > Attachments: ejb-configs.sh, jboss-ejb-client.xml, server(transaction).log, thread-dump-stop-1.txt > > > I'm testing wildfly 20.0.1 (and 21.0.2 was tested too) for replace our old version of Wildfly 10. > it happens that frequently we have seen that the stop function of server does not work and we need to kill the process by manual operation on the OS. > It sounds like a dead look. > I attatch the thread dump on this. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14077) Some tests hang indefinitely when using security manager on JDK 11.0.8 & JDK 11.0.9

by Richard Opalka (Jira)

[ https://issues.redhat.com/browse/WFLY-14077?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFLY-14077: ---------------------------------- Summary: Some tests hang indefinitely when using security manager on JDK 11.0.8 & JDK 11.0.9 (was: Some tests hang indefinitely when using security manager and JDK 11) > Some tests hang indefinitely when using security manager on JDK 11.0.8 & JDK 11.0.9 > ----------------------------------------------------------------------------------- > > Key: WFLY-14077 > URL: https://issues.redhat.com/browse/WFLY-14077 > Project: WildFly > Issue Type: Task > Components: Security Manager > Reporter: Bartosz Spyrko-Smietanko > Assignee: Richard Opalka > Priority: Major > Attachments: stacktrace.log > > > Some tests hang indefinitely when using security manager and JDK 11 : e.g. AuthenticationForwardingSFSFTestCase.java , AuthenticationForwardingSLSFTestCase.java -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2021