April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13406) Update layersTest to recognize bootable jar runtime

by Jean Francois Denise (Jira)

Jean Francois Denise created WFLY-13406: ------------------------------------------- Summary: Update layersTest to recognize bootable jar runtime Key: WFLY-13406 URL: https://issues.redhat.com/browse/WFLY-13406 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Jean Francois Denise Assignee: Jean Francois Denise -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2474) Messages about dropped queued message when using IpAddressUUID

by Mirko Streckenbach (Jira)

Mirko Streckenbach created JGRP-2474: ---------------------------------------- Summary: Messages about dropped queued message when using IpAddressUUID Key: JGRP-2474 URL: https://issues.redhat.com/browse/JGRP-2474 Project: JGroups Issue Type: Bug Affects Versions: 4.2.3 Reporter: Mirko Streckenbach Assignee: Bela Ban Attachments: JGR.java, log-fail-1.txt We upgraded from 4.0.14 to 4.1.8 and ever since then, we had some messages like {code} Apr 27, 2020 10:30:54 AM org.jgroups.protocols.UNICAST3 addQueuedMessages WARNING: i2:1709: dropped queued message i1:1609#2 as its conn_id (0) did not match (entry.conn_id=1) {code} when ever an application is restarted. Our setup is as follows (most due to network restrictions): * Fixed port numbers * JDBC_PING * We use IpAddressUUID in order to have a "readable" information in the jgroupsping table I could track this down to 4.1.2 / 4.1.3: 4.1.2 works as expected, from 4.1.3 I'm seeing the effect observed above. I attached a simple example that demonstrates the problem: starts two stacks, shuts down the second (non-coordindator) and starts it again after a couple of seconds. With 4.1.2 this works as expected (no warnings), but 4.1.3 and more recent versions (including 4.2.3) produce warnings. The exact behavior is not completely consistent: in most cases, starting the second app again results in some timeouts and the second app becomes a coordinator itself and a merge view is established later (log attached). In some cases it only creates the warnings shown above (this is what we observe in our real application) and in some cases everything works fine. I don't have any warnings in the log if I don't set an AddressGenerator, but I'd like to avoid this. While running this on higher debug levels, I observed the following: 4.1.2 will not require an ACK for the LEAVE_RSP message. 4.1.3 will. The second app sends the ACK, but the coordinator does not seem to receive or process it properly and retransmits the LEAVE_RSP message again and again. This is independent of the AddressGenerator used, -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1132) Automate OCP disconnected testing

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1132?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1132: ---------------------------------- Sprint: Kiali Sprint #38, Kiali Sprint #39 (was: Kiali Sprint #38) > Automate OCP disconnected testing > --------------------------------- > > Key: SWSQE-1132 > URL: https://issues.redhat.com/browse/SWSQE-1132 > Project: Kiali QE > Issue Type: Story > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > SM on disconnected OCP cluster will be the main feature of SM 1.1.1 > We need to automate testing of that. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1136) Automate AuthPolicy adding https://github.com/kiali/kiali-ui/pull/1747

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1136?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1136: ---------------------------------- Sprint: Kiali Sprint #38, Kiali Sprint #39 (was: Kiali Sprint #38) > Automate AuthPolicy adding https://github.com/kiali/kiali-ui/pull/1747 > ---------------------------------------------------------------------- > > Key: SWSQE-1136 > URL: https://issues.redhat.com/browse/SWSQE-1136 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1056) Try OCP 4.4 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 (was: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38) > Try OCP 4.4 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)

6 years

1
0
0 / 0

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

6 years

1
0
0 / 0

[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 (was: Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38) > 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)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1113) Smee client is ignoring some merge PR commits

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1113?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1113: ---------------------------------- Sprint: Kiali Sprint #38, Kiali Sprint #39 (was: Kiali Sprint #38) > Smee client is ignoring some merge PR commits > --------------------------------------------- > > Key: SWSQE-1113 > URL: https://issues.redhat.com/browse/SWSQE-1113 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Some push events from kiali and kiali-ui repos are missed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1117) New kiali operator repo

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1117?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1117: ---------------------------------- Sprint: Kiali Sprint #38, Kiali Sprint #39 (was: Kiali Sprint #38) > New kiali operator repo > ----------------------- > > Key: SWSQE-1117 > URL: https://issues.redhat.com/browse/SWSQE-1117 > Project: Kiali QE > Issue Type: Story > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Critical > Labels: infrastructure > > There is a new kiali operator repo which we need to use in our pipelines. > https://github.com/kiali/kiali-operator -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1125) Update job parameters for jaeger

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1125?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1125: ---------------------------------- Sprint: Kiali Sprint #38, Kiali Sprint #39 (was: Kiali Sprint #38) > Update job parameters for jaeger > -------------------------------- > > Key: SWSQE-1125 > URL: https://issues.redhat.com/browse/SWSQE-1125 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We are still using parameters for jaeger like: > JAEGER_OPERATOR_HUB=quay.io/maistra > JAEGER_OPERATOR_IMAGE=jaeger-rhel7-operator > JAEGER_OPERATOR_TAG=latest-qe > JAEGER_HUB=quay.io/maistra > JAEGER_TAG=latest-qe > We need to make it optional as it's not necessary when using OLM. > Remember to update default values and PR jobs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 April 2020