May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-140) Kiali-UI Test Framework Using kiali-python-client

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-140?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-140: --------------------------------- Sprint: Kiali QE Sprint 4, Kiali QE Sprint 5 (was: Kiali QE Sprint 4) > Kiali-UI Test Framework Using kiali-python-client > ------------------------------------------------- > > Key: SWSQE-140 > URL: https://issues.jboss.org/browse/SWSQE-140 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-140) Kiali-UI Test Framework Using kiali-python-client

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-140?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan reassigned SWSQE-140: ------------------------------------ Assignee: Hayk Hovsepyan (was: Michael Foley) > Kiali-UI Test Framework Using kiali-python-client > ------------------------------------------------- > > Key: SWSQE-140 > URL: https://issues.jboss.org/browse/SWSQE-140 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-161) Create Jenkins Job To Push Out Latest Kiali - For Community Usage

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-161?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-161. -------------------------------- Resolution: Done > Create Jenkins Job To Push Out Latest Kiali - For Community Usage > ----------------------------------------------------------------- > > Key: SWSQE-161 > URL: https://issues.jboss.org/browse/SWSQE-161 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Note: Could be that we leverage the existing CD pipeline for this task. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-159) Communicty Available Kiali Build - Latest and Greatest

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-159?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-159. -------------------------------- Resolution: Done > Communicty Available Kiali Build - Latest and Greatest > ------------------------------------------------------ > > Key: SWSQE-159 > URL: https://issues.jboss.org/browse/SWSQE-159 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Development requests for making the latest Kiali version (aka: latest PR) available for community use. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10350) Duplicated packages in artemis modules

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-10350?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFLY-10350: ------------------------------------ An initial check indicates that the classes of the duplicated package(s) in these two JARs may not overlap, so it may not be a bug. [~jmesnil] should confirm, and maybe at some point we could put a comment in the module.xml to that effect. > Duplicated packages in artemis modules > -------------------------------------- > > Key: WFLY-10350 > URL: https://issues.jboss.org/browse/WFLY-10350 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 12.0.0.Final > Reporter: Erich Duda > Assignee: Jeff Mesnil > > As you can see in the following report, some Artemis packages are present in multiple jars which are parts of different modules. {{artemis-core-client}} jar is located in main module and {{artemis-commons}} jar is located in {{journal}} module. This is problem for Jigsaw. > Based on the discussion with [~dmlloyd] This can be solved by adding {{filter}} subelement to the artemis-commons to filter out duplicated packages. > {code} > 142) [Package org.apache.activemq.artemis.api.core is present in multiple jars [artemis-commons-1.5.5.jbossorg-010.jar, artemis-core-client-1.5.5.jbossorg-010.jar]] > 144) [Package org.apache.activemq.artemis.core.buffers.impl is present in multiple jars [artemis-commons-1.5.5.jbossorg-010.jar, artemis-core-client-1.5.5.jbossorg-010.jar]] > ./org/apache/activemq/artemis/main/artemis-core-client-1.5.5.jbossorg-010.jar > ./org/apache/activemq/artemis/journal/main/artemis-commons-1.5.5.jbossorg-010.jar > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-161) Create Jenkins Job To Push Out Latest Kiali - For Community Usage

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-161?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-161: ------------------------------------ Jenkins job: [http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Nightly%20Public...] > Create Jenkins Job To Push Out Latest Kiali - For Community Usage > ----------------------------------------------------------------- > > Key: SWSQE-161 > URL: https://issues.jboss.org/browse/SWSQE-161 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Note: Could be that we leverage the existing CD pipeline for this task. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-160) Setup Openshift Cluster For Communicy Kiali Instance

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-160?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-160. -------------------------------- Resolution: Done > Setup Openshift Cluster For Communicy Kiali Instance > ---------------------------------------------------- > > Key: SWSQE-160 > URL: https://issues.jboss.org/browse/SWSQE-160 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-159) Communicty Available Kiali Build - Latest and Greatest

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-159?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-159: ------------------------------- Sprint: Kiali QE Sprint 5 > Communicty Available Kiali Build - Latest and Greatest > ------------------------------------------------------ > > Key: SWSQE-159 > URL: https://issues.jboss.org/browse/SWSQE-159 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Development requests for making the latest Kiali version (aka: latest PR) available for community use. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3813) Remove usages of deprecated ServiceController.getImmediateUnavailableDependencies() method

by Richard Opalka (JIRA)

Richard Opalka created WFCORE-3813: -------------------------------------- Summary: Remove usages of deprecated ServiceController.getImmediateUnavailableDependencies() method Key: WFCORE-3813 URL: https://issues.jboss.org/browse/WFCORE-3813 Project: WildFly Core Issue Type: Enhancement Components: Server Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 5.0.0.Beta1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-200) B12 OpenShift Cluster is flaky

by Kevin Earls (JIRA)

[ https://issues.jboss.org/browse/SWSQE-200?page=com.atlassian.jira.plugin.... ] Kevin Earls commented on SWSQE-200: ----------------------------------- As a quick update, when I logged into B12 today my Jenkins instance in the jaeger-test project was inaccessible. There were no events nor anything in the logs which gave any indication of what the problem might be. I eventually reduced Jenkins down to 0 pods and then back up to 1 in order to restart it. Even so it seemed to take 15-20 minutes before it was available again, as opposed to 3 or 4 minutes normally. > B12 OpenShift Cluster is flaky > ------------------------------ > > Key: SWSQE-200 > URL: https://issues.jboss.org/browse/SWSQE-200 > Project: Kiali QE > Issue Type: QE Task > Reporter: Kevin Earls > Assignee: Guilherme Baufaker Rêgo > > I'm opening this mostly as a placeholder, and will update it as I get more information on the problems I've been experiencing. Since I've been using B12 I've been experiencing more frequent failures than on other clusters, including minishift on my laptop and the CNCF CI Jenkins. Here are a couple of instances: > 1. Deploying ElasticSearch along with the Jaeger Production templates requires allocating 2G or memory, even though the default 512M works fine elsewhere. This can be seen in the Jaeger Standalone Performance tests job here: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/J... . If you run the job without changing the ES_MEMORY parameter to 2Gi it will fail. > 2. I have a set of smoke tests for Red Hat productized artifacts for the Jaeger Java client which are run using the Jaeger all-in-one template. It's fairly simple, but on B12 deployment of the Jaeger all-in-one images fails on every other build. I've made a copy of the job here: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/F... and its history should be clear. > So far I have not been able to get any useful information about why this is failing. In the OpenShift console it looks like Jaeger has started correctly. There are no errors in the logs, nor any to be found under monitoring. But if you click on the Jaeger link, you get the message "Application is not available . The application is currently not serving requests at this endpoint. It may not have been started or is still starting." -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 May 2018