May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3845) Upgrade commons-logging-jboss-logging from 1.0.0.Beta1 to 1.0.0.Final

by James Perkins (JIRA)

James Perkins created WFCORE-3845: ------------------------------------- Summary: Upgrade commons-logging-jboss-logging from 1.0.0.Beta1 to 1.0.0.Final Key: WFCORE-3845 URL: https://issues.jboss.org/browse/WFCORE-3845 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Priority: Blocker Fix For: 5.0.0.Beta2 Upgrade the {{org.jboss.logging:commons-logging-jboss-logging}} from 1.0.0.Beta1 to 1.0.0.Final. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10228) Upgrade Picketlink Bindings from 2.5.5.SP10 to 2.5.5.SP11

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10228?page=com.atlassian.jira.plugin... ] Lin Gao updated WFLY-10228: --------------------------- Description: https://github.com/jbossas/redhat-picketlink-bindings/compare/v2.5.5.SP10... and https://github.com/jbossas/redhat-picketlink/compare/v2.5.5.SP10...eap-7.x > Upgrade Picketlink Bindings from 2.5.5.SP10 to 2.5.5.SP11 > --------------------------------------------------------- > > Key: WFLY-10228 > URL: https://issues.jboss.org/browse/WFLY-10228 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Lin Gao > Assignee: Vladimir Dosoudil > Labels: downstream_dependency > > https://github.com/jbossas/redhat-picketlink-bindings/compare/v2.5.5.SP10... > and > https://github.com/jbossas/redhat-picketlink/compare/v2.5.5.SP10...eap-7.x -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10228) Upgrade Picketlink from 2.5.5.SP10 to 2.5.5.SP11

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10228?page=com.atlassian.jira.plugin... ] Lin Gao updated WFLY-10228: --------------------------- Summary: Upgrade Picketlink from 2.5.5.SP10 to 2.5.5.SP11 (was: Upgrade Picketlink Bindings from 2.5.5.SP10 to 2.5.5.SP11) > Upgrade Picketlink from 2.5.5.SP10 to 2.5.5.SP11 > ------------------------------------------------ > > Key: WFLY-10228 > URL: https://issues.jboss.org/browse/WFLY-10228 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Lin Gao > Assignee: Vladimir Dosoudil > Labels: downstream_dependency > > https://github.com/jbossas/redhat-picketlink-bindings/compare/v2.5.5.SP10... > and > https://github.com/jbossas/redhat-picketlink/compare/v2.5.5.SP10...eap-7.x -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-213) Add B13 to Openshift cluster 3

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-213?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-213. ------------------------------------------- Resolution: Done > Add B13 to Openshift cluster 3 > ------------------------------ > > Key: SWSQE-213 > URL: https://issues.jboss.org/browse/SWSQE-213 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > Because SWSQE-200, it is better moving b13 to openshift cluster 3 than openshift cluster 1. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-213) Add B13 to Openshift cluster 3

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-213?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-213: ----------------------------------------------- Added B13 to Openshift Cluster 3 > Add B13 to Openshift cluster 3 > ------------------------------ > > Key: SWSQE-213 > URL: https://issues.jboss.org/browse/SWSQE-213 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > Because SWSQE-200, it is better moving b13 to openshift cluster 3 than openshift cluster 1. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-207) Openshift New OS Cluster with b24 and b25

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-207?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-207. ------------------------------------------- Resolution: Done > Openshift New OS Cluster with b24 and b25 > ------------------------------------------ > > Key: SWSQE-207 > URL: https://issues.jboss.org/browse/SWSQE-207 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3786) ManagementAuthenticationUsersTestCase fails on latest JDKs

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3786?page=com.atlassian.jira.plugi... ] David Lloyd commented on WFCORE-3786: ------------------------------------- Looks like I accidentally removed a critical package in the MODULES-369 commit. I've done a second PR to fix it up, and I'm now retesting locally before I send in the component update. > ManagementAuthenticationUsersTestCase fails on latest JDKs > ---------------------------------------------------------- > > Key: WFCORE-3786 > URL: https://issues.jboss.org/browse/WFCORE-3786 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Richard Opalka > Assignee: Darran Lofthouse > Fix For: 5.0.0.Beta2 > > > I downloaded both jdk1.8.0_b171 & jdk1.8.0_b172. > When running whole WFCORE test suite on them > I'm getting InvalidUserStore exception in > ManagementAuthenticationUsersTestCase -- 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 Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-200?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-200. ------------------------------------------- Resolution: Done > 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: Minor > > 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] (SWSQE-200) B12 OpenShift Cluster is flaky

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-200?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo edited comment on SWSQE-200 at 5/14/18 10:41 AM: ------------------------------------------------------------------------- [~kearls] I have created persistent storage on b12 and b24, also fixed the issue with ansible-broker I think we may need to open an issue for Elasticsearch to 1G. Since this issue is not a blocker, I am closing this issue. was (Author: gbaufake): [~kearls] I have created persistent storage on b12 and b24, also fixed the issue with ansible-broker I think we may need to open an issue for Elasticsearch to 1G. Since this issue is not a blocker, I am closing this issues. > 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: Minor > > 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] (SWSQE-200) B12 OpenShift Cluster is flaky

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-200?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-200: ----------------------------------------------- [~kearls] I have created persistent storage on b12 and b24, also fixed the issue with ansible-broker I think we may need to open an issue for Elasticsearch to 1G. Since this issue is not a blocker, I am closing this issues. > 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: Minor > > 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