February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2293) Graceful concurrent leaving of coordinator(s) leaves the cluster with stale views

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/JGRP-2293?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on JGRP-2293: ------------------------------------ [~belaban] I ran our test suite a few times without reproducing the failure. Then I got the idea to repeat the offending test 100 times, and I got it to fail both with JGroups 4.0.15.Final and with 4.0.17-SNAPSHOT. Finally I analyzed the logs and I think it is a problem with the test itself, so the fix is good for me. I still haven't managed to run {{LeaveTest}} successfully from the command line though, the nodes never form a cluster because they don't see each other's MPING requests. If I run without {{<jvmarg value="-Djava.net.preferIPv4Stack=true"/>}} I get a sendto error (see below), but with it I get no error message, the nodes just don't see each other. I'd say it's a problem with my environment, but the same test using the same mcast address (230.0.5.6.7) passes when run from the IDE. {noformat} 12:55:16,177 ERROR (main:[]) [MPING] JGRP000200: failed sending discovery request java.io.IOException: Invalid argument (sendto failed) at java.net.PlainDatagramSocketImpl.send(Native Method) ~[?:1.8.0_171] at java.net.DatagramSocket.send(DatagramSocket.java:693) ~[?:1.8.0_171] at org.jgroups.protocols.MPING.sendMcastDiscoveryRequest(MPING.java:306) [classes/:?] at org.jgroups.protocols.PING.sendDiscoveryRequest(PING.java:64) [classes/:?] at org.jgroups.protocols.PING.findMembers(PING.java:32) [classes/:?] {noformat} > Graceful concurrent leaving of coordinator(s) leaves the cluster with stale views > --------------------------------------------------------------------------------- > > Key: JGRP-2293 > URL: https://issues.jboss.org/browse/JGRP-2293 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.14 > Reporter: Radoslav Husar > Assignee: Bela Ban > Priority: Critical > Fix For: 4.0.17 > > Attachments: IMG_20190123_124154.jpg > > > JGroups does not handle concurrent leaving of nodes correctly. This is a typical use case in cloud environment when scaled down with an autoscaler/manually which we need to handle. > A simple test can be devised which fails first n (where n>1) nodes from a cluster, reproducer PR https://github.com/belaban/JGroups/pull/397 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2262) [DMN Designer] DRD Grid Column width is not preserved

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2262?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2262: ------------------------------------- [~manstis] [~danielezonca] I am sorry for my wrong assumption. Thank you for an explanation. > [DMN Designer] DRD Grid Column width is not preserved > ----------------------------------------------------- > > Key: DROOLS-2262 > URL: https://issues.jboss.org/browse/DROOLS-2262 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > DND Grid Column don't preserve the width. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-508) Automate - Services List 'Error Rate' field

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-508?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan deleted SWSQE-508: --------------------------------- > Automate - Services List 'Error Rate' field > ------------------------------------------- > > Key: SWSQE-508 > URL: https://issues.jboss.org/browse/SWSQE-508 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-505) Automate - Workloads List Error Rate field

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-505?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan deleted SWSQE-505: --------------------------------- > Automate - Workloads List Error Rate field > ------------------------------------------ > > Key: SWSQE-505 > URL: https://issues.jboss.org/browse/SWSQE-505 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-526) UI Tests - Make version compatible to run for TP

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-526?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-526: -------------------------------- Sprint: Kiali Sprint #14, Kiali Sprint #17, Kiali Sprint #18 (was: Kiali Sprint #14, Kiali Sprint #17) > UI Tests - Make version compatible to run for TP > ------------------------------------------------ > > Key: SWSQE-526 > URL: https://issues.jboss.org/browse/SWSQE-526 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Filip Brychta > Priority: Major > > Currently when Kiali is released with older version than latest master, UI tests is not possible to run: > 1. UI tests are not tagged. > 2. Kiali REST Client is always latest on jenkins slaves. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-587) Python broken in jenkins-slave-kiali-ui-tests-python3

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-587?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-587. --------------------------------- Resolution: Done Fixed python bin to point to python2, python3 points to python3.6. Pip and pytest are from python3. Also consolidated jenkins-slave-kiali-ui-tests and jenkins-slave-kiali-ui-tests-python3 to one and removed old jenkins job run-python-ui-tests. The same problem was in jenkins-slave-kiali-rest-tests. Update slave labels and doc https://mojo.redhat.com/docs/DOC-1168333 > Python broken in jenkins-slave-kiali-ui-tests-python3 > ----------------------------------------------------- > > Key: SWSQE-587 > URL: https://issues.jboss.org/browse/SWSQE-587 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > > sh-4.2$ yum > sh: /usr/bin/yum: /usr/bin/python: bad interpreter: No such file or directory > sh-4.2$ python > sh: python: command not found > sh-4.2$ > Check other slaves as well -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-554) Add missing Openshift API calls

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-554?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-554. ---------------------------------- Resolution: Done > Add missing Openshift API calls > ------------------------------- > > Key: SWSQE-554 > URL: https://issues.jboss.org/browse/SWSQE-554 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Currently there are several areas in UI tests that do not have call to Openshift API for data comparison. > 1. Figure out which calls are missing to Openshift. > 2. Create API call. > 3. Create assertions on that results to compare with UI data. > 4. PR per area (API call). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-554) Add missing Openshift API calls

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-554?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-554: --------------------------------- Sprint: Kiali Sprint #16, Kiali Sprint #17 (was: Kiali Sprint #16, Kiali Sprint #17, Kiali Sprint #18) > Add missing Openshift API calls > ------------------------------- > > Key: SWSQE-554 > URL: https://issues.jboss.org/browse/SWSQE-554 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Currently there are several areas in UI tests that do not have call to Openshift API for data comparison. > 1. Figure out which calls are missing to Openshift. > 2. Create API call. > 3. Create assertions on that results to compare with UI data. > 4. PR per area (API call). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-554) Add missing Openshift API calls

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-554?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-554: --------------------------------- Sprint: Kiali Sprint #16, Kiali Sprint #17, Kiali Sprint #18 (was: Kiali Sprint #16, Kiali Sprint #17, Kiali Sprint #18) > Add missing Openshift API calls > ------------------------------- > > Key: SWSQE-554 > URL: https://issues.jboss.org/browse/SWSQE-554 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Currently there are several areas in UI tests that do not have call to Openshift API for data comparison. > 1. Figure out which calls are missing to Openshift. > 2. Create API call. > 3. Create assertions on that results to compare with UI data. > 4. PR per area (API call). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-554) Add missing Openshift API calls

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-554?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-554: --------------------------------- Sprint: Kiali Sprint #16, Kiali Sprint #17, Kiali Sprint #18 (was: Kiali Sprint #16, Kiali Sprint #17) > Add missing Openshift API calls > ------------------------------- > > Key: SWSQE-554 > URL: https://issues.jboss.org/browse/SWSQE-554 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Currently there are several areas in UI tests that do not have call to Openshift API for data comparison. > 1. Figure out which calls are missing to Openshift. > 2. Create API call. > 3. Create assertions on that results to compare with UI data. > 4. PR per area (API call). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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 February 2019