August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12409) Javaee8 BOM should include all spec artifacts directly

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12409: -------------------------------------- Summary: Javaee8 BOM should include all spec artifacts directly Key: WFLY-12409 URL: https://issues.jboss.org/browse/WFLY-12409 Project: WildFly Issue Type: Enhancement Components: BOM Reporter: Eduardo Martins Assignee: Eduardo Martins ... instead of importing through JBoss Specs BOM, which WildFly does not uses and thus its dependency management may be out of sync. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12408) Upgrade jboss-concurrency-api_1.0_spec from 1.0.2.Final to 2.0.0.CR1

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12408?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12408: ----------------------------------- Summary: Upgrade jboss-concurrency-api_1.0_spec from 1.0.2.Final to 2.0.0.CR1 (was: Upgrade jboss-concurrency-api_1.0_spec from 1.0.2.Final to 2.0.0.Final) > Upgrade jboss-concurrency-api_1.0_spec from 1.0.2.Final to 2.0.0.CR1 > -------------------------------------------------------------------- > > Key: WFLY-12408 > URL: https://issues.jboss.org/browse/WFLY-12408 > Project: WildFly > Issue Type: Sub-task > Components: Concurrency Utilities > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12408) Upgrade jboss-concurrency-api_1.0_spec from 1.0.2.Final to 2.0.0.Final

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12408: -------------------------------------- Summary: Upgrade jboss-concurrency-api_1.0_spec from 1.0.2.Final to 2.0.0.Final Key: WFLY-12408 URL: https://issues.jboss.org/browse/WFLY-12408 Project: WildFly Issue Type: Sub-task Components: Concurrency Utilities Reporter: Eduardo Martins Assignee: Eduardo Martins -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-218) Jakarta Concurrency Javadocs should have original Eclipse Foundation footer

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/JBEE-218?page=com.atlassian.jira.plugin.s... ] Eduardo Martins updated JBEE-218: --------------------------------- Git Pull Request: https://github.com/jboss/jboss-jakarta-concurrency-api/pull/4 > Jakarta Concurrency Javadocs should have original Eclipse Foundation footer > --------------------------------------------------------------------------- > > Key: JBEE-218 > URL: https://issues.jboss.org/browse/JBEE-218 > Project: JBoss Enterprise Spec APIs > Issue Type: Bug > Components: jboss-javaee-concurrency-api > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > The original javadoc plugin config should be restored, so the proper Eclipse Foundation footer is kept in the fork's javadoc -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-218) Jakarta Concurrency Javadocs should have original Eclipse Foundation footer

by Eduardo Martins (Jira)

Eduardo Martins created JBEE-218: ------------------------------------ Summary: Jakarta Concurrency Javadocs should have original Eclipse Foundation footer Key: JBEE-218 URL: https://issues.jboss.org/browse/JBEE-218 Project: JBoss Enterprise Spec APIs Issue Type: Bug Components: jboss-javaee-concurrency-api Reporter: Eduardo Martins Assignee: Eduardo Martins The original javadoc plugin config should be restored, so the proper Eclipse Foundation footer is kept in the fork's javadoc -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4617) jboss-cli.sh does not error on invalid options such as --controler

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFCORE-4617?page=com.atlassian.jira.plugi... ] Jean Francois Denise commented on WFCORE-4617: ---------------------------------------------- Yes, that is a good suggestion, we can safely detect at the end of the checks that it is an unsupported argument when it starts by "-". > jboss-cli.sh does not error on invalid options such as --controler > ------------------------------------------------------------------ > > Key: WFCORE-4617 > URL: https://issues.jboss.org/browse/WFCORE-4617 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Minor > > If the --controller is not spelled correctly, the CLI is ignoring it and then trying to connect to the default localhost:9990 in from the jboss-cli.xml. This makes it look like there is a connection error when the actual issue is the option passed to the CLI is not a valid option. > {code} > ./bin/standalone.sh -Djboss.socket.binding.port-offset=9 > {code} > {code} > /bin/jboss-cli.sh --controler=myhost:9999 --connect > Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-941) Kiali is now available without /kiali suffix in URL

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-941?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-941: ------------------------------------- This commit caused that: https://github.com/Maistra/istio-operator/commit/14c3a446f860683b93abce9e... By default context is not set so no /kiali suffix > Kiali is now available without /kiali suffix in URL > --------------------------------------------------- > > Key: SWSQE-941 > URL: https://issues.jboss.org/browse/SWSQE-941 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Blocker > Labels: infrastructure > > Kiali is from RC1 available without /kiali suffix in URL. We need to find out why and update our pipelines -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-941) Kiali is now available without /kiali suffix in URL

by Filip Brychta (Jira)

Filip Brychta created SWSQE-941: ----------------------------------- Summary: Kiali is now available without /kiali suffix in URL Key: SWSQE-941 URL: https://issues.jboss.org/browse/SWSQE-941 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta Kiali is from RC1 available without /kiali suffix in URL. We need to find out why and update our pipelines -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-176) Pod restarted because of failing liveness/rediness Probe

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-176?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-176: ------------------------------------ [~tradej] Note, there is behavioural change between 72 images and 73 images tracked in this issue. Where previous behaviour was more bug. And it behaves correctly now. We will need somehow inform user about that change. Not sure what will be the best place in documentation. It will be something similar to what will be created in under https://issues.jboss.org/browse/JBEAP-16858 for 72 + OCP4. > Pod restarted because of failing liveness/rediness Probe > -------------------------------------------------------- > > Key: WFWIP-176 > URL: https://issues.jboss.org/browse/WFWIP-176 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ken Wills > Priority: Major > > During testing 73 image I came to case where really corner case is tested [0]. > Test is not using templates for deployment. > In tested scenario liveness/readiness probe fails. In CD 17 and eap 73 pod is restarted. In CD 16 however, there was no liveness/rediness failures in events. Pod was not restarted. > I dont see differences in pod yaml for CD16 case > {code} > livenessProbe: > exec: > command: > - /bin/bash > - '-c' > - /opt/eap/bin/livenessProbe.sh > failureThreshold: 3 > periodSeconds: 10 > successThreshold: 1 > timeoutSeconds: 1 > name: weirdusername > readinessProbe: > exec: > command: > - /bin/bash > - '-c' > - /opt/eap/bin/readinessProbe.sh > failureThreshold: 3 > periodSeconds: 10 > successThreshold: 1 > timeoutSeconds: 1 > {code} > and CD 17 case > {code} > livenessProbe: > exec: > command: > - /bin/bash > - '-c' > - /opt/eap/bin/livenessProbe.sh > failureThreshold: 3 > periodSeconds: 10 > successThreshold: 1 > timeoutSeconds: 1 > name: weirdusername > readinessProbe: > exec: > command: > - /bin/bash > - '-c' > - /opt/eap/bin/readinessProbe.sh > failureThreshold: 3 > periodSeconds: 10 > successThreshold: 1 > timeoutSeconds: 1 > {code} > What could cause this behaviour change? > [0] https://issues.jboss.org/browse/CLOUD-1988 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-176) Pod restarted because of failing liveness/rediness Probe

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-176?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFWIP-176: ------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) (was: Documentation (Ref Guide, User Guide, etc.),Release Notes) > Pod restarted because of failing liveness/rediness Probe > -------------------------------------------------------- > > Key: WFWIP-176 > URL: https://issues.jboss.org/browse/WFWIP-176 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ken Wills > Priority: Major > > During testing 73 image I came to case where really corner case is tested [0]. > Test is not using templates for deployment. > In tested scenario liveness/readiness probe fails. In CD 17 and eap 73 pod is restarted. In CD 16 however, there was no liveness/rediness failures in events. Pod was not restarted. > I dont see differences in pod yaml for CD16 case > {code} > livenessProbe: > exec: > command: > - /bin/bash > - '-c' > - /opt/eap/bin/livenessProbe.sh > failureThreshold: 3 > periodSeconds: 10 > successThreshold: 1 > timeoutSeconds: 1 > name: weirdusername > readinessProbe: > exec: > command: > - /bin/bash > - '-c' > - /opt/eap/bin/readinessProbe.sh > failureThreshold: 3 > periodSeconds: 10 > successThreshold: 1 > timeoutSeconds: 1 > {code} > and CD 17 case > {code} > livenessProbe: > exec: > command: > - /bin/bash > - '-c' > - /opt/eap/bin/livenessProbe.sh > failureThreshold: 3 > periodSeconds: 10 > successThreshold: 1 > timeoutSeconds: 1 > name: weirdusername > readinessProbe: > exec: > command: > - /bin/bash > - '-c' > - /opt/eap/bin/readinessProbe.sh > failureThreshold: 3 > periodSeconds: 10 > successThreshold: 1 > timeoutSeconds: 1 > {code} > What could cause this behaviour change? > [0] https://issues.jboss.org/browse/CLOUD-1988 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 August 2019