May 2018 - jboss-jira - Jboss List Archives

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

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-200?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-200: ------------------------------- Priority: Blocker (was: Major) > 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 > Priority: Blocker > > 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

[JBoss JIRA] (WFCORE-3818) Improved console color capability detection

by David Lloyd (JIRA)

David Lloyd created WFCORE-3818: ----------------------------------- Summary: Improved console color capability detection Key: WFCORE-3818 URL: https://issues.jboss.org/browse/WFCORE-3818 Project: WildFly Core Issue Type: Enhancement Components: Logging, Scripts Reporter: David Lloyd We should improve on our ability to correctly detect color capabilities on the console. Many times, build logs in CI environments and similar cases are hard to read due to ANSI codes being written to a console that did not have color capabilities, and this could have been detected. In the bash scripts, logic like the following can be used: * If the {{tput}} command does not exist, fall back to checking {{TERM}}. * If {{tput colors}} returns 8, 16, or 256, the terminal supports at least that many colors. * The {{TERM}} var: the terminal supports 256 colors if {{TERM}] contains values xterm-256color, screen-256color, or generally any value containing 256 probably indicates color support. * Check the value of the COLORTERM environment variable; if truecolor or 24bit, then you have 24-bit RGB capability (this should apply to Linux, Mac OS X, and Windows). On Windows, COLORTERM is also usually supported in terminals supporting 24-bit RGB; presence of this env var may be sufficient to enable color. The TERM environment variable is also often supported. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-206) Investegate b21 & b12 Docker Failures

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-206: ---------------------------------- Summary: Investegate b21 & b12 Docker Failures Key: SWSQE-206 URL: https://issues.jboss.org/browse/SWSQE-206 Project: Kiali QE Issue Type: Task Reporter: Matt Mahoney Assignee: Michael Foley Priority: Minor Docker periodical needs to be restarted, which is causing pod failures. This issue appears to have started when clusters were upgraded to OS3.9. Investigate reason for failures. Resolve if at all possible. Temp work-around: 1) Restart docker service 2) Reboot instance if #1 failed -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-194) ISTIOOC Client

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-194?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-194. -------------------------------- Resolution: Done Covered by other Jiras. > ISTIOOC Client > --------------- > > Key: SWSQE-194 > URL: https://issues.jboss.org/browse/SWSQE-194 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Michael Foley > > [ Jenkins ISTIO Install] script doesn't use the istiooc client that Kevin has been building. > Right now there are issues with the ansible-installer that cause few errors - I don't know what exactly the issues are, but Kevin is aware and has it in his to-do list to patch and send a PR very soon. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-102) create maven caching proxy

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-102?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-102. -------------------------------- Resolution: Done > create maven caching proxy > -------------------------- > > Key: SWSQE-102 > URL: https://issues.jboss.org/browse/SWSQE-102 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > Create maven caching proxy to skip download from internet everytime -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-174) Openshift Clusters

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-174?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-174: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo > Openshift Clusters > ------------------ > > Key: SWSQE-174 > URL: https://issues.jboss.org/browse/SWSQE-174 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-144) Kiali-Test-Mesh Deployer Jenkins Job Enancement To Deploy Sub-Set

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-144?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-144: ------------------------------------------ Parent: SWSQE-145 Issue Type: Sub-task (was: Task) > Kiali-Test-Mesh Deployer Jenkins Job Enancement To Deploy Sub-Set > ----------------------------------------------------------------- > > Key: SWSQE-144 > URL: https://issues.jboss.org/browse/SWSQE-144 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Minor > > Currently the Jenkins Job that deploys Kial-Test-Mesh deploys all possible test meshes + Traffic Generator for each mesh. Some Openshift Clusters do no have the resources to support all meshes. > Thus, enhance the Jenkins deployer job to deploy all OR a sub-et of all possible meshes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-144) Kiali-Test-Mesh Deployer Jenkins Job Enancement To Deploy Sub-Set

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-144?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-144: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Kiali-Test-Mesh Deployer Jenkins Job Enancement To Deploy Sub-Set > ----------------------------------------------------------------- > > Key: SWSQE-144 > URL: https://issues.jboss.org/browse/SWSQE-144 > Project: Kiali QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Minor > > Currently the Jenkins Job that deploys Kial-Test-Mesh deploys all possible test meshes + Traffic Generator for each mesh. Some Openshift Clusters do no have the resources to support all meshes. > Thus, enhance the Jenkins deployer job to deploy all OR a sub-et of all possible meshes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-133) Configure passwordless ssh access from jenkins slaves

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-133?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-133: ------------------------------- Sprint: Kiali QE Sprint 5 > Configure passwordless ssh access from jenkins slaves > ----------------------------------------------------- > > Key: SWSQE-133 > URL: https://issues.jboss.org/browse/SWSQE-133 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-131) Research Central CI message BUS

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-131?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-131: ------------------------------- Sprint: Kiali QE Sprint 5 > Research Central CI message BUS > ------------------------------- > > Key: SWSQE-131 > URL: https://issues.jboss.org/browse/SWSQE-131 > Project: Kiali QE > Issue Type: QE Task > Reporter: Michael Foley > Assignee: Guilherme Baufaker Rêgo > Priority: Minor > > Research Central CI message in order to have collaboration between teams (Istio, Kiali, Jaeger) -- 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