June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1184) OC API - Service list - Add health

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1184: ------------------------------------- Summary: OC API - Service list - Add health Key: SWSQE-1184 URL: https://issues.redhat.com/browse/SWSQE-1184 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan openshift_api.service_list # TODO: heath needs to be added -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1183) OC API - Application list - Add health

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1183: ------------------------------------- Summary: OC API - Application list - Add health Key: SWSQE-1183 URL: https://issues.redhat.com/browse/SWSQE-1183 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan openshift_api.application_list TODO: health needs to be added -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss 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: ---------------------------------- Issue Type: Task (was: Bug) > DropDown - Optimization of hierarchy. > ------------------------------------- > > Key: SWSQE-1182 > URL: https://issues.redhat.com/browse/SWSQE-1182 > Project: Kiali QE > Issue Type: Task > Reporter: 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 (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1181) DropDown - Check open and close states first - optimize

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1181?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1181: ---------------------------------- Issue Type: Task (was: Bug) > DropDown - Check open and close states first - optimize > ------------------------------------------------------- > > Key: SWSQE-1181 > URL: https://issues.redhat.com/browse/SWSQE-1181 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13578) Add a testcase for transaction propagation over EJB remote simulating network issues on remote calls

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-13578?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka edited comment on WFLY-13578 at 6/17/20 7:41 AM: ------------------------------------------------------------------ I've created the tests https://github.com/ochaloup/wildfly/commits/JBEAP-19435-openshift-do-not-... but for being able to create PR I'm waiting for resolution on WFTC-85 was (Author: ochaloup): I've created the tests https://github.com/ochaloup/wildfly/commits/JBEAP-19435-openshift-do-not-... but for I'm able to create PR I'm waiting for resolution on WFTC-85 > Add a testcase for transaction propagation over EJB remote simulating network issues on remote calls > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-13578 > URL: https://issues.redhat.com/browse/WFLY-13578 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 20.0.0.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The WFLY integration testsuite misses integration tests for EJB remote calls which comes with transaction propagation which would simlate network issues during 2PC processing. > > There was recently added a testcase WFLY-13516 but there is still missing a test for issue JBEAP-19435. > > The testcase should be verifying that if transaction intermittently fails during commit phase of 2PC then the transaction recovery processing is capable to finish with commit. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1179) Migrate the Mirror Catalog Jobs from Operator Source to Catalog Source

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1179?page=com.atlassian.jira.plugi... ] Filip Brychta closed SWSQE-1179. -------------------------------- Resolution: Duplicate Issue Dup of SWSQE-1176 > Migrate the Mirror Catalog Jobs from Operator Source to Catalog Source > ---------------------------------------------------------------------- > > Key: SWSQE-1179 > URL: https://issues.redhat.com/browse/SWSQE-1179 > Project: Kiali QE > Issue Type: QE Task > Reporter: Guilherme Baufaker Rêgo > Priority: Major > > The job is still using the old operator-source. > > We should migrate to the new catalog-sources. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1180) Red Hat Operators Mirroring is not working on Disconnected Clusters

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1180?page=com.atlassian.jira.plugi... ] Filip Brychta updated SWSQE-1180: --------------------------------- Labels: infrastructure (was: ) Sprint: Kiali Sprint #41 > Red Hat Operators Mirroring is not working on Disconnected Clusters > ------------------------------------------------------------------- > > Key: SWSQE-1180 > URL: https://issues.redhat.com/browse/SWSQE-1180 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > Attachments: Captura de Tela 2020-06-16 às 20.07.23.png > > > [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/infra-jobs/job...] > > [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/install-ocp-upi...] > > Failed to pull image "bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators:v1": rpc error: code = Unknown desc = Error reading manifest v1 in bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators: manifest unknown: manifest unknown > > > It seems the mirroring is not working on the PSI cluster with the mirror job. > picture attached. > > > > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1180) Red Hat Operators Mirroring is not working on Disconnected Clusters

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1180?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1180. ---------------------------------- Resolution: Done The issue you saw is caused by a recent OCP bug - https://bugzilla.redhat.com/show_bug.cgi?id=1838375 I added a workaround to the mirroring job. > Red Hat Operators Mirroring is not working on Disconnected Clusters > ------------------------------------------------------------------- > > Key: SWSQE-1180 > URL: https://issues.redhat.com/browse/SWSQE-1180 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > Attachments: Captura de Tela 2020-06-16 às 20.07.23.png > > > [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/infra-jobs/job...] > > [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/install-ocp-upi...] > > Failed to pull image "bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators:v1": rpc error: code = Unknown desc = Error reading manifest v1 in bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators: manifest unknown: manifest unknown > > > It seems the mirroring is not working on the PSI cluster with the mirror job. > picture attached. > > > > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13592) [GSS] (7.3.z) jndi-view doen't show values for EJB in java:jboss/exported

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-13592?page=com.atlassian.jira.plugi... ] Parul Sharma moved JBEAP-19712 to WFLY-13592: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-13592 (was: JBEAP-19712) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB Naming (was: EJB) (was: Naming) Affects Version/s: (was: 7.3.0.GA) Fix Version/s: (was: 7.3.3.GA) > [GSS] (7.3.z) jndi-view doen't show values for EJB in java:jboss/exported > ------------------------------------------------------------------------- > > Key: WFLY-13592 > URL: https://issues.redhat.com/browse/WFLY-13592 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Reporter: Parul Sharma > Assignee: Parul Sharma > Priority: Major > > jndi-view() show values as '?' for EJB on java:jboss/exported tree. > These values could be seen on EAP 6.4. > This can be reproduced on EAP 7.3.1 and 7.2.8. > I attached a reproducer and these results as follows. > reproducer.zip > jndi_view_result_731.txt > jndi_view_result_6422.txt > > EAP 7.3.1 / 7.2.8 > {code} > [standalone@localhost:9990 /] /subsystem=naming:jndi-view() > ... > "java:jboss/exported" => { > "ejb2-1.0" => { > "class-name" => "javax.naming.Context", > "children" => { > "GreeterEJB!com.example.GreeterEJBHome" => { > "class-name" => "java.lang.Object", > "value" => "?" > }, > "GreeterEJB!com.example.GreeterEJBRemote" => { > "class-name" => "java.lang.Object", > "value" => "?" > } > } > }, > "ejb3-1.0" => { > "class-name" => "javax.naming.Context", > "children" => {"GreeterEJB!com.example.GreeterRemote" => { > "class-name" => "java.lang.Object", > "value" => "?" > }} > } > }, > {code} > > EAP 6.4 > {code} > "java:jboss/exported" => { > "ejb2-1.0" => { > "class-name" => "javax.naming.Context", > "children" => { > "GreeterEJB!com.example.GreeterEJBHome" => { > "class-name" => "com.example.GreeterEJBHome", > "value" => "Proxy for remote EJB EJBHomeLocator{appName='', moduleName='ejb2-1.0', distinctName='', beanName='GreeterEJB', view='interface com.example.GreeterEJBHome'}" > }, > "GreeterEJB!com.example.GreeterEJBRemote" => { > "class-name" => "com.example.GreeterEJBRemote", > "value" => "Proxy for remote EJB StatelessEJBLocator{appName='', moduleName='ejb2-1.0', distinctName='', beanName='GreeterEJB', view='interface com.example.GreeterEJBRemote'}" > } > } > }, > "ejb3-1.0" => { > "class-name" => "javax.naming.Context", > "children" => {"GreeterEJB!com.example.GreeterRemote" => { > "class-name" => "com.example.GreeterRemote", > "value" => "Proxy for remote EJB StatelessEJBLocator{appName='', moduleName='ejb3-1.0', distinctName='', beanName='GreeterEJB', view='interface com.example.GreeterRemote'}" > }} > } > }, > {code} > > Additionally, > If EJB3 doesn't have @Remote, values are '?' in 'java:global' and 'java:app' similarly. > The following behaviour is not changed from 6.4. But it seems a sililar behavir as the above. > I attached the reproducer and these results as follows. > reproducer_without_remote_if.zip > jndi_view_result_no_remoteif_731.txt > jndi_view_result_no_remoteif_6422.txt > EAP 7.3.1 > {code} > "java:global" => { > ... > "ejb3-1.0" => { > "class-name" => "javax.naming.Context", > "children" => { > "GreeterEJB" => { > "class-name" => "com.example.GreeterEJB", > "value" => "?" > }, > "GreeterEJB!com.example.GreeterEJB" => { > "class-name" => "com.example.GreeterEJB", > "value" => "?" > } > } > } > } > }, > "applications" => { > "ejb3-1.0.jar" => { > "java:app" => { > ... > "ejb3-1.0" => { > "class-name" => "javax.naming.Context", > "children" => { > "GreeterEJB" => { > "class-name" => "com.example.GreeterEJB", > "value" => "?" > }, > "GreeterEJB!com.example.GreeterEJB" => { > "class-name" => "com.example.GreeterEJB", > "value" => "?" > } > } > } > }, > "modules" => undefined > }, > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

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

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1182: ------------------------------------- Summary: DropDown - Optimization of hierarchy. Key: SWSQE-1182 URL: https://issues.redhat.com/browse/SWSQE-1182 Project: Kiali QE Issue Type: Bug Reporter: Hayk Hovsepyan Currently there is a big hierarchy of DropDown objects. It needs to be optimized. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020