jboss-jira October 2019

jboss-jira@lists.jboss.org

1 participants
1855 discussions

[JBoss JIRA] (WFWIP-215) Operator headless service labeled with wildfly.org/operated-by-loadbalancer=active

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFWIP-215?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka commented on WFWIP-215: ---------------------------------------- [~mchoma] thank you for pointing that out. This error happened because of the code refactoring which occured last week. The fix is part of the PR https://github.com/wildfly/wildfly-operator/pull/90 > Operator headless service labeled with wildfly.org/operated-by-loadbalancer=active > ---------------------------------------------------------------------------------- > > Key: WFWIP-215 > URL: https://issues.jboss.org/browse/WFWIP-215 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ondrej Chaloupka > Priority: Blocker > > # create the WildflyServer CR > {code:yaml} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > name: eap-cd > namespace: mchoma > spec: > applicationImage: >- > image-registry.openshift-image-registry.svc:5000/eapcd-suite-builds/eap-cd-openshift-rhel8:17.0-4 > env: [] > envFrom: [] > size: 1 > {code} > # Both services {{eap-cd-headless}} and {{eap-cd-loadbalancer}} created by Operator have same labels. We used to select service based on label wildfly.org/operated-by-loadbalancer. > {code} > eap-cd-headless > app.kubernetes.io/managed-by=eap-operator > app.kubernetes.io/name=eap-cd > app.openshift.io/runtime=eap > wildfly.org/operated-by-loadbalancer=active > eap-cd-loadbalancer > app.kubernetes.io/managed-by=eap-operator > app.kubernetes.io/name=eap-cd > app.openshift.io/runtime=eap > wildfly.org/operated-by-loadbalancer=active > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-215) Operator headless service labeled with wildfly.org/operated-by-loadbalancer=active

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-215?page=com.atlassian.jira.plugin.... ] Jeff Mesnil reassigned WFWIP-215: --------------------------------- Assignee: Ondrej Chaloupka (was: Jeff Mesnil) > Operator headless service labeled with wildfly.org/operated-by-loadbalancer=active > ---------------------------------------------------------------------------------- > > Key: WFWIP-215 > URL: https://issues.jboss.org/browse/WFWIP-215 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ondrej Chaloupka > Priority: Blocker > > # create the WildflyServer CR > {code:yaml} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > name: eap-cd > namespace: mchoma > spec: > applicationImage: >- > image-registry.openshift-image-registry.svc:5000/eapcd-suite-builds/eap-cd-openshift-rhel8:17.0-4 > env: [] > envFrom: [] > size: 1 > {code} > # Both services {{eap-cd-headless}} and {{eap-cd-loadbalancer}} created by Operator have same labels. We used to select service based on label wildfly.org/operated-by-loadbalancer. > {code} > eap-cd-headless > app.kubernetes.io/managed-by=eap-operator > app.kubernetes.io/name=eap-cd > app.openshift.io/runtime=eap > wildfly.org/operated-by-loadbalancer=active > eap-cd-loadbalancer > app.kubernetes.io/managed-by=eap-operator > app.kubernetes.io/name=eap-cd > app.openshift.io/runtime=eap > wildfly.org/operated-by-loadbalancer=active > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12614) Duplicated ConstraintViolation message

by Robin Schimpf (Jira)

Robin Schimpf created WFLY-12614: ------------------------------------ Summary: Duplicated ConstraintViolation message Key: WFLY-12614 URL: https://issues.jboss.org/browse/WFLY-12614 Project: WildFly Issue Type: Bug Affects Versions: 18.0.0.Beta1, 17.0.1.Final Reporter: Robin Schimpf Assignee: Brian Stansberry Attachments: wildfly-bug.zip We currently are upgrading our application from Wildfly 13 to Wildfly 17.0.1 and are receiving duplicated constraint violations in the response of an invalid request. Interestingly Wildfly 13 also seems to be not behaving correctly on the third request but in another way. There is the violation exception returned in the response instead of the duplicated value Wildfly 17 is returning now. I also tested this on the currently available Wildfly 18 Beta 1 and the issue is also reproducible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4690) Fix test suite tests to work with Eclipse OpenJ9

by James Perkins (Jira)

James Perkins created WFCORE-4690: ------------------------------------- Summary: Fix test suite tests to work with Eclipse OpenJ9 Key: WFCORE-4690 URL: https://issues.jboss.org/browse/WFCORE-4690 Project: WildFly Core Issue Type: Task Components: Test Suite Reporter: James Perkins Assignee: James Perkins Some tests fail when Eclipse OpenJ9 is the JVM. In most cases there are specific changes for the IBM J9 JVM which can be ported over to support both Eclipse OpenJ9 and IBM J9. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11990) Make opentracing an optional dependency of observability layer

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11990?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11990: ------------------------------------ Issue Type: Enhancement (was: Feature Request) > Make opentracing an optional dependency of observability layer > -------------------------------------------------------------- > > Key: WFLY-11990 > URL: https://issues.jboss.org/browse/WFLY-11990 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > Fix For: 18.0.0.Final > > > It appears that the opentracing should have its own 'open-tracing' layer. > observability layer should have an optional dependency on open-tracing layer. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

← Newer
1
...
183
184
185
186
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019