October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-253) With operator it is not possible to mount configMap to $JBOSS_HOME/extensions

by Ken Wills (Jira)

[ https://issues.jboss.org/browse/WFWIP-253?page=com.atlassian.jira.plugin.... ] Ken Wills commented on WFWIP-253: --------------------------------- [~jmesnil] These are executed via openshift-launch: https://github.com/jboss-container-images/jboss-eap-modules/blob/7.3.x-le... https://github.com/jboss-container-images/jboss-eap-modules/blob/7.3.x-le... $JBOSS_HOME/extensions is the required location for it, its special in the sense that when it runs all other configuration should be completed, and any remaining XML markers etc in teh config file are no longer required etc. So on EAP 7.2, for example it would be safe to run the embedded CLI at this point, and not be concerned about XML markers / comments being dropped from the config. > With operator it is not possible to mount configMap to $JBOSS_HOME/extensions > ----------------------------------------------------------------------------- > > Key: WFWIP-253 > URL: https://issues.jboss.org/browse/WFWIP-253 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Simka > Assignee: Jeff Mesnil > Priority: Major > Labels: operator > > With operator it is not possible to mount configMap to $JBOSS_HOME/extensions. Which is supported way how to run postconfigure scripts. > See: https://issues.jboss.org/browse/EAP7-892?focusedCommentId=13684369&page=c... > Operator mounts all configMaps to {{/etc/configmaps}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12682) Update EE Security Subsystem to use Phases from WildFly Core

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-12682: --------------------------------------- Summary: Update EE Security Subsystem to use Phases from WildFly Core Key: WFLY-12682 URL: https://issues.jboss.org/browse/WFLY-12682 Project: WildFly Issue Type: Bug Components: EE, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 19.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12681) Create 'microprofile' layer spec

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12681?page=com.atlassian.jira.plugin... ] Brian Stansberry edited comment on WFLY-12681 at 10/17/19 10:45 AM: -------------------------------------------------------------------- I changed this to Feature Request as it's a feature. It perhaps ends up being a task under some other feature, but the basic thing about how to distribute and install the MP specs as an aggregate is a feature. was (Author: brian.stansberry): I changed this to Feature Request as it's a feature. It perhaps ends up being a task under some other feature, but the basic thing about how to distribute and install the MP specs as an aggregate is a feature. I'll file an EAP7. > Create 'microprofile' layer spec > -------------------------------- > > Key: WFLY-12681 > URL: https://issues.jboss.org/browse/WFLY-12681 > Project: WildFly > Issue Type: Feature Request > Components: Build System > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > We used to have a 'microprofile' layer spec aggregating all MP specs which at the moment only contained config, health and metrics which got renamed to 'observability' by WFLY-11774. > With the introduction of new specs fault tolerance, openapi, etc. we should reintroduce the 'microprofile' layer spec which contains all of the MP specs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12681) Create 'microprofile' layer spec

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12681?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12681: ----------------------------------------- I changed this to Feature Request as it's a feature. It perhaps ends up being a task under some other feature, but the basic thing about how to distribute and install the MP specs as an aggregate is a feature. I'll file an EAP7. > Create 'microprofile' layer spec > -------------------------------- > > Key: WFLY-12681 > URL: https://issues.jboss.org/browse/WFLY-12681 > Project: WildFly > Issue Type: Feature Request > Components: Build System > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > We used to have a 'microprofile' layer spec aggregating all MP specs which at the moment only contained config, health and metrics which got renamed to 'observability' by WFLY-11774. > With the introduction of new specs fault tolerance, openapi, etc. we should reintroduce the 'microprofile' layer spec which contains all of the MP specs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4717) Add missing phases for EE Security subsystem

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4717: ---------------------------------------- Summary: Add missing phases for EE Security subsystem Key: WFCORE-4717 URL: https://issues.jboss.org/browse/WFCORE-4717 Project: WildFly Core Issue Type: Bug Components: Server Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 11.0.0.Beta2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12681) Create 'microprofile' layer spec

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12681?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12681: ------------------------------------ Issue Type: Feature Request (was: Task) > Create 'microprofile' layer spec > -------------------------------- > > Key: WFLY-12681 > URL: https://issues.jboss.org/browse/WFLY-12681 > Project: WildFly > Issue Type: Feature Request > Components: Build System > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > We used to have a 'microprofile' layer spec aggregating all MP specs which at the moment only contained config, health and metrics which got renamed to 'observability' by WFLY-11774. > With the introduction of new specs fault tolerance, openapi, etc. we should reintroduce the 'microprofile' layer spec which contains all of the MP specs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-254) Changes in volumeClaimTemplate triggers creation of a new statefulset

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-254?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-254: ----------------------------------- [~pkremens]That's not a bug: the VCT of a statefulset can not be updated. It requires to recreate the statefulset. I don't have a running example atm but you should be able to reproduce by creating a vanilla statefulset and update its vct. The kubectl edit command will reject the update > Changes in volumeClaimTemplate triggers creation of a new statefulset > --------------------------------------------------------------------- > > Key: WFWIP-254 > URL: https://issues.jboss.org/browse/WFWIP-254 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Petr Kremensky > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > Adding a volumeClaimTemplate, or existing an existing one leads to the re-creation of statefulset -> all pods are immediately terminated and route is unavailable until some of the pods is ready again. > *reproduce* > * deploy operator {noformat}./build/run-openshift.sh{noformat} > * deploy updatedquickstart project from operator repository {noformat}cat deploy/crds/quickstart-cr.yaml > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > name: quickstart > spec: > applicationImage: "quay.io/wildfly-quickstarts/wildfly-operator-quickstart:18.0" > replicas: 2 > storage: > volumeClaimTemplate: > spec: > resources: > requests: > storage: 1Mi > oc apply -f deploy/crds/quickstart-cr.yaml{noformat} > * wait for both replicas to be ready & print ss creation timestamp & verify application readiness {noformat}oc get pods > NAME READY STATUS RESTARTS AGE > quickstart-0 1/1 Running 0 2m48s > quickstart-1 1/1 Running 0 2m48s > wildfly-operator-54455dbcd8-flnd4 1/1 Running 0 69m > oc get statefulset.apps/quickstart --template={{.metadata.creationTimestamp}} > 2019-10-17T13:55:03Z > curl quickstart-route-wildfly.apps-crc.testing > {"ip":"10.128.1.36"} > {noformat} > * edit the storage field (e.g. storage: 1Mi -> storage: 2Mi) > * notice the both pods are terminating, stateful set creation timestamp has changed and application route is not available until one of the pods will start again (could take a minute){noformat}oc get pods > NAME READY STATUS RESTARTS AGE > quickstart-0 1/1 Terminating 0 5m42s > quickstart-1 1/1 Terminating 0 5m42s > wildfly-operator-54455dbcd8-flnd4 1/1 Running 0 72m > oc get statefulset.apps/quickstart --template={{.metadata.creationTimestamp}} > 2019-10-17T14:00:44Z > curl quickstart-route-wildfly.apps-crc.testing > ... > Application is not available > ... > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12111) Upgrade picketlink to 2.5.5.SP13

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFLY-12111?page=com.atlassian.jira.plugin... ] Teresa Miyar Gil reassigned WFLY-12111: --------------------------------------- Assignee: (was: Teresa Miyar Gil) > Upgrade picketlink to 2.5.5.SP13 > -------------------------------- > > Key: WFLY-12111 > URL: https://issues.jboss.org/browse/WFLY-12111 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Teresa Miyar Gil > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12125) Integration test for PLINK-793

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFLY-12125?page=com.atlassian.jira.plugin... ] Teresa Miyar Gil reassigned WFLY-12125: --------------------------------------- Assignee: (was: Teresa Miyar Gil) > Integration test for PLINK-793 > ------------------------------ > > Key: WFLY-12125 > URL: https://issues.jboss.org/browse/WFLY-12125 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 17.0.0.Alpha1 > Reporter: Teresa Miyar Gil > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12125) Integration test for PLINK-793

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFLY-12125?page=com.atlassian.jira.plugin... ] Teresa Miyar Gil reassigned WFLY-12125: --------------------------------------- Assignee: Teresa Miyar Gil > Integration test for PLINK-793 > ------------------------------ > > Key: WFLY-12125 > URL: https://issues.jboss.org/browse/WFLY-12125 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 17.0.0.Alpha1 > Reporter: Teresa Miyar Gil > Assignee: Teresa Miyar Gil > Priority: Major > Labels: downstream_dependency > -- 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