October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELYWEB-68) Upgrade Travis CI to OpenJDK 11

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-68?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELYWEB-68: ----------------------------- Fix Version/s: 1.7.0.CR1 > Upgrade Travis CI to OpenJDK 11 > ------------------------------- > > Key: ELYWEB-68 > URL: https://issues.jboss.org/browse/ELYWEB-68 > Project: Elytron Web > Issue Type: Task > Components: Testsuite > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.7.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-68) Upgrade Travis CI to OpenJDK 11

by Farah Juma (Jira)

Farah Juma created ELYWEB-68: -------------------------------- Summary: Upgrade Travis CI to OpenJDK 11 Key: ELYWEB-68 URL: https://issues.jboss.org/browse/ELYWEB-68 Project: Elytron Web Issue Type: Task Components: Testsuite Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-246) management-common.sh not copied to image.

by Jean Francois Denise (Jira)

Jean Francois Denise created WFWIP-246: ------------------------------------------ Summary: management-common.sh not copied to image. Key: WFWIP-246 URL: https://issues.jboss.org/browse/WFWIP-246 Project: WildFly WIP Issue Type: Bug Reporter: Jean Francois Denise Assignee: Jean Francois Denise -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12313) Integrate MicroProfile OpenAPI 1.1

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12313?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-12313: -------------------------------- Summary: Integrate MicroProfile OpenAPI 1.1 (was: Integrate MicroProfile OpenAPI) > Integrate MicroProfile OpenAPI 1.1 > ---------------------------------- > > Key: WFLY-12313 > URL: https://issues.jboss.org/browse/WFLY-12313 > Project: WildFly > Issue Type: Feature Request > Reporter: Michael Edgar > Assignee: Paul Ferraro > Priority: Major > > Please integrate MicroProfile OpenAPI. > Details about MP OpenAPI: > https://github.com/eclipse/microprofile-open-api/releases/tag/1.1.2 > Maybe it is possible to use SmallRye implementation: > https://github.com/smallrye/smallrye-open-api -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-67) A doPrivileged it required to access the JASPI AuthConfigFactory

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELYWEB-67?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELYWEB-67: ----------------------------------- Fix Version/s: 1.7.0.CR1 > A doPrivileged it required to access the JASPI AuthConfigFactory > ---------------------------------------------------------------- > > Key: ELYWEB-67 > URL: https://issues.jboss.org/browse/ELYWEB-67 > Project: Elytron Web > Issue Type: Bug > Components: Undertow Servlet > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.7.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-975) Jaeger operator fails to deploy because of registry puller not being accessible yet

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-975?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-975. --------------------------------- Resolution: Done https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/commit/... > Jaeger operator fails to deploy because of registry puller not being accessible yet > ----------------------------------------------------------------------------------- > > Key: SWSQE-975 > URL: https://issues.jboss.org/browse/SWSQE-975 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Jaeger operator installation fails with: > Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "registry-puller.kevinconner.io": Post https://registry-puller.registry-puller.svc:443/webhook?timeout=30s: no endpoints available for service "registry-puller" > It's happening only sometimes so I guess it depends on registry puller pod startup time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-67) A doPrivileged it required to access the JASPI AuthConfigFactory

by Darran Lofthouse (Jira)

Darran Lofthouse created ELYWEB-67: -------------------------------------- Summary: A doPrivileged it required to access the JASPI AuthConfigFactory Key: ELYWEB-67 URL: https://issues.jboss.org/browse/ELYWEB-67 Project: Elytron Web Issue Type: Bug Components: Undertow Servlet Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12657) KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update

by Martin Simka (Jira)

[ https://issues.jboss.org/browse/WFLY-12657?page=com.atlassian.jira.plugin... ] Martin Simka commented on WFLY-12657: ------------------------------------- likely it could be reproduced by following https://github.com/wildfly/wildfly-operator/tree/master/examples/clustering > KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > -------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12657 > URL: https://issues.jboss.org/browse/WFLY-12657 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Martin Simka > Assignee: Radoslav Husar > Priority: Major > > In my test application on openshift KUBE_PING logs warning every 20-30s . > {noformat} > 13:27:05,340 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:27:40,600 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:27:40,600 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:27:57,892 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:27:57,892 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:28:21,104 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:28:21,104 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:28:45,737 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:28:45,737 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:29:05,335 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:29:05,335 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:29:29,027 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:29:29,027 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:30:04,195 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:30:04,195 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12297) Jakarta EE 8 Certification for WildFly

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12297?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-12297: ------------------------------------- Thanks Brian, I think it is fine to resolve now, as it looks like we will be approved as per [https://github.com/eclipse-ee4j/jakartaee-platform/issues/121] + [https://github.com/eclipse-ee4j/jakartaee-platform/issues/120] > Jakarta EE 8 Certification for WildFly > -------------------------------------- > > Key: WFLY-12297 > URL: https://issues.jboss.org/browse/WFLY-12297 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Scott Marlow > Priority: Blocker > Fix For: 18.0.0.Final > > > Certify WildFly 18 as Jakarta EE 8 compatible. Publish the certification results on https://github.com/wildfly/certifications -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4637) Test concurrency behaviour when an update status is received during the consumeBuffer as a Leader and as A Replica

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4637?page=com.atlassian.jira.plugi... ] Massimiliano Dessi commented on DROOLS-4637: -------------------------------------------- [~danielezonca] > Test concurrency behaviour when an update status is received during the consumeBuffer as a Leader and as A Replica > ------------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-4637 > URL: https://issues.jboss.org/browse/DROOLS-4637 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 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 October 2019