October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4482) Out of the box SSL with Wildfly Elytron

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4482?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4482: -------------------------------- Fix Version/s: 11.0.0.Beta2 (was: 11.0.0.Beta1) > Out of the box SSL with Wildfly Elytron > --------------------------------------- > > Key: WFCORE-4482 > URL: https://issues.jboss.org/browse/WFCORE-4482 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Labels: EAP-CD19 > Fix For: 11.0.0.Beta2 > > > The details of this RFE will be explored within the analysis, presently Undertow depends on a security-realm that generates a self signed cert on start up so we will require an Elytron equivalent. > There may be opportunities to tie this in in some way with the new CA integration support but that can be explored in the analysis. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4713) Migrate controller module to new MSC API

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4713?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4713: -------------------------------- Fix Version/s: 11.0.0.Beta2 (was: 11.0.0.Beta1) > Migrate controller module to new MSC API > ---------------------------------------- > > Key: WFCORE-4713 > URL: https://issues.jboss.org/browse/WFCORE-4713 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: Richard Opalka > Assignee: Jeff Mesnil > Priority: Major > 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] (WFCORE-4700) Add dependency on elytron-jwt

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4700?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4700: -------------------------------- Fix Version/s: 11.0.0.Beta2 (was: 11.0.0.Beta1) > Add dependency on elytron-jwt > ----------------------------- > > Key: WFCORE-4700 > URL: https://issues.jboss.org/browse/WFCORE-4700 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 11.0.0.Beta2 > > > This is only being added to Core as this is where the remaining Elytron dependencies come in - the module will be added in WildFly with the relevant subsystem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4670) Upgrade JBoss MSC to 1.4.12.Final

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4670?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4670: -------------------------------- Fix Version/s: 11.0.0.Beta2 (was: 11.0.0.Beta1) > Upgrade JBoss MSC to 1.4.12.Final > --------------------------------- > > Key: WFCORE-4670 > URL: https://issues.jboss.org/browse/WFCORE-4670 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Katarina Hermanova > Assignee: Richard Opalka > Priority: Major > 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] (WFCORE-4584) Include the new wildfly-elytron-encryption module

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4584?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4584: -------------------------------- Fix Version/s: 11.0.0.Beta2 (was: 11.0.0.Beta1) > Include the new wildfly-elytron-encryption module > ------------------------------------------------- > > Key: WFCORE-4584 > URL: https://issues.jboss.org/browse/WFCORE-4584 > Project: WildFly Core > Issue Type: Sub-task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > 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] (WFCORE-4583) Add SecretKey manipulation operations to the credential-store resource

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4583?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4583: -------------------------------- Fix Version/s: 11.0.0.Beta2 (was: 11.0.0.Beta1) > Add SecretKey manipulation operations to the credential-store resource > ---------------------------------------------------------------------- > > Key: WFCORE-4583 > URL: https://issues.jboss.org/browse/WFCORE-4583 > Project: WildFly Core > Issue Type: Sub-task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > 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] (WFWIP-252) Error log messages in operator logs on CRD edit after scale down

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-252?page=com.atlassian.jira.plugin.... ] Petr Kremensky commented on WFWIP-252: -------------------------------------- {noformat} {"level":"error","ts":1571208568.7673173,"logger":"wildlfyserver_resources","msg":"Failed to update resource","WildFlyServer.Namespace":"pkremens-namespace","WildFlyServer.Name":"simple-jaxrs-health-eap-cd","Resource.Name":"simple-jaxrs-health-eap-cd","Resource.Type":"*v1.StatefulSet","error":"Operation cannot be fulfilled on statefulsets.apps \"simple-jaxrs-health-eap-cd\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/wildfly/wildfly-operator/vendor/github.com/go-logr/zapr.(*zapL..."} {"level":"error","ts":1571208568.7674172,"logger":"wildflyserver_controller","msg":"Failed to update StatefulSet.","StatefulSet.Namespace":"pkremens-namespace","StatefulSet.Name":"simple-jaxrs-health-eap-cd","error":"Operation cannot be fulfilled on statefulsets.apps \"simple-jaxrs-health-eap-cd\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/wildfly/wildfly-operator/vendor/github.com/go-logr/zapr.(*zapL..."} {"level":"error","ts":1571208568.7675304,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"pkremens-namespace/simple-jaxrs-health-eap-cd","error":"Operation cannot be fulfilled on statefulsets.apps \"simple-jaxrs-health-eap-cd\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/wildfly/wildfly-operator/vendor/github.com/go-logr/zapr.(*zapL..."} {noformat} This is the one I'm trying to hit now ^ > Error log messages in operator logs on CRD edit after scale down > ---------------------------------------------------------------- > > Key: WFWIP-252 > URL: https://issues.jboss.org/browse/WFWIP-252 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Petr Kremensky > Assignee: Jeff Mesnil > Priority: Major > Labels: operator > Attachments: operator-logs.txt > > > Error messages can be found in operator logs after user performs a scale down task (WFWIP-251) and than edit the CRD. > *reproduce* > * deploy operator {noformat}./build/run-openshift.sh{noformat} > * change the default number of initial replicas from 2 to 3 {noformat}sed -i 's/2/3/' deploy/crds/quickstart-cr.yaml{noformat} > * deploy quickstart project from operator repository {noformat}oc apply -f deploy/crds/quickstart-cr.yaml{noformat} > * wait for both replicas to be ready {noformat}oc get pods > NAME READY STATUS RESTARTS AGE > quickstart-0 1/1 Running 0 31s > quickstart-1 1/1 Running 0 31s > quickstart-2 1/1 Running 0 31s > wildfly-operator-5bcb545b46-j788h 1/1 Running 0 41s{noformat} > * scale down to 2 {noformat}oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/replicas", "value":2}]' --type json{noformat} > * wait for scale down to perform {noformat} Pods: > Name: quickstart-0 > Pod IP: 10.128.1.193 > State: ACTIVE > Name: quickstart-1 > Pod IP: 10.128.1.192 > State: ACTIVE > Replicas: 2 > Scalingdown Pods: 0 > {noformat} > * edit the CRD (e.g. add an env variable) {noformat}oc edit wildflyserver quickstart > ... > replicas: 2 > env: > - name: FOO > value: BAR{noformat} > * wait for both pods to be reloaded > * see the [^operator-logs.txt] > ** apart WFWIP-251, there are 2 extra error messages > There might be other ways to reproduce the issue, but these should make it 100% appearance (at least for me). > *actual* > Error messages in operator log > {noformat} > {"level":"error","ts":1571215869.7030337,"logger":"wildlfyserver_resources","msg":"Failed to update resource","WildFlyServer.Namespace":"wildfly-test","WildFlyServer.Name":"quickstart","Resource.Name":"quickstart","Resource.Type":"*v1.StatefulSet","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."} > {"level":"error","ts":1571215869.7032435,"logger":"wildflyserver_controller","msg":"Failed to update StatefulSet.","StatefulSet.Namespace":"wildfly-test","StatefulSet.Name":"quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."} > {"level":"error","ts":1571215869.7034042,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"wildfly-test/quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."} > {noformat} > *expected* > No error messages in operator log. > Operator image build from [0a221ea|https://github.com/wildfly/wildfly-operator/commit/0a221eac5eb462...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-250) How to install operator to watch list of namespaces?

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-250?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-250: ----------------------------------- The file deploy/operator-group.yaml is only used to test the EAP operator when it is not installed through Red Hat OperatorHub. I set only the eap-operator as a target for the operator but it should be possible to remove it so that the operator listens on all namespaces as documented in https://docs.openshift.com/dedicated/4/applications/operators/olm-underst... When the EAP Operator is installed through the EAP Operator, it will listen for namespaces defined in the olm.targetNamespaces as expected. > How to install operator to watch list of namespaces? > ---------------------------------------------------- > > Key: WFWIP-250 > URL: https://issues.jboss.org/browse/WFWIP-250 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > > We do not have eap operator on the stage OperatorHub WFWIP-232, so I could not try myself. But this questions arise. > {code:yaml|title=deploy/configmap-eap-operator.gen.yaml} > ... > deployments: > - name: eap-operator > spec: > replicas: 1 > selector: > matchLabels: > name: eap-operator > strategy: {} > template: > metadata: > labels: > name: eap-operator > spec: > containers: > - command: > - wildfly-operator > env: > - name: WATCH_NAMESPACE > valueFrom: > fieldRef: > fieldPath: metadata.annotations['olm.targetNamespaces'] > ... > {code} > {code:yaml|title=deploy/operator-group.yaml} > apiVersion: operators.coreos.com/v1 > kind: OperatorGroup > metadata: > name: example > namespace: eap-operator > spec: > targetNamespaces: > - eap-operator > {code} > 1. Does it mean operator by default watch only {{eap-operator}} namespace? Will that be parametrized in Web Console? > 2. If user want to install operator to watch multiple/all namespaces how should he do? Will that be exposed in Web Console? > If I try to edit {{WATCH_NAMESPACE}} on eap-operator Deployment it is owerwriten back to > {code} > valueFrom: > fieldRef: > apiVersion: v1 > fieldPath: 'metadata.annotations[''olm.targetNamespaces'']' > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-252) Error log messages in operator logs on CRD edit after scale down

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-252?page=com.atlassian.jira.plugin.... ] Petr Kremensky closed WFWIP-252. -------------------------------- Resolution: Done Closing this one for now, this one is equivalent to WFWIP-251, there was another error, I cannot find a way to reproduce that now. > Error log messages in operator logs on CRD edit after scale down > ---------------------------------------------------------------- > > Key: WFWIP-252 > URL: https://issues.jboss.org/browse/WFWIP-252 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Petr Kremensky > Assignee: Jeff Mesnil > Priority: Major > Labels: operator > Attachments: operator-logs.txt > > > Error messages can be found in operator logs after user performs a scale down task (WFWIP-251) and than edit the CRD. > *reproduce* > * deploy operator {noformat}./build/run-openshift.sh{noformat} > * change the default number of initial replicas from 2 to 3 {noformat}sed -i 's/2/3/' deploy/crds/quickstart-cr.yaml{noformat} > * deploy quickstart project from operator repository {noformat}oc apply -f deploy/crds/quickstart-cr.yaml{noformat} > * wait for both replicas to be ready {noformat}oc get pods > NAME READY STATUS RESTARTS AGE > quickstart-0 1/1 Running 0 31s > quickstart-1 1/1 Running 0 31s > quickstart-2 1/1 Running 0 31s > wildfly-operator-5bcb545b46-j788h 1/1 Running 0 41s{noformat} > * scale down to 2 {noformat}oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/replicas", "value":2}]' --type json{noformat} > * wait for scale down to perform {noformat} Pods: > Name: quickstart-0 > Pod IP: 10.128.1.193 > State: ACTIVE > Name: quickstart-1 > Pod IP: 10.128.1.192 > State: ACTIVE > Replicas: 2 > Scalingdown Pods: 0 > {noformat} > * edit the CRD (e.g. add an env variable) {noformat}oc edit wildflyserver quickstart > ... > replicas: 2 > env: > - name: FOO > value: BAR{noformat} > * wait for both pods to be reloaded > * see the [^operator-logs.txt] > ** apart WFWIP-251, there are 2 extra error messages > There might be other ways to reproduce the issue, but these should make it 100% appearance (at least for me). > *actual* > Error messages in operator log > {noformat} > {"level":"error","ts":1571215869.7030337,"logger":"wildlfyserver_resources","msg":"Failed to update resource","WildFlyServer.Namespace":"wildfly-test","WildFlyServer.Name":"quickstart","Resource.Name":"quickstart","Resource.Type":"*v1.StatefulSet","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."} > {"level":"error","ts":1571215869.7032435,"logger":"wildflyserver_controller","msg":"Failed to update StatefulSet.","StatefulSet.Namespace":"wildfly-test","StatefulSet.Name":"quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."} > {"level":"error","ts":1571215869.7034042,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"wildfly-test/quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."} > {noformat} > *expected* > No error messages in operator log. > Operator image build from [0a221ea|https://github.com/wildfly/wildfly-operator/commit/0a221eac5eb462...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-252) Error log messages in operator logs on CRD edit after scale down

by Petr Kremensky (Jira)

Petr Kremensky created WFWIP-252: ------------------------------------ Summary: Error log messages in operator logs on CRD edit after scale down Key: WFWIP-252 URL: https://issues.jboss.org/browse/WFWIP-252 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Petr Kremensky Assignee: Jeff Mesnil Attachments: operator-logs.txt Error messages can be found in operator logs after user performs a scale down task (WFWIP-251) and than edit the CRD. *reproduce* * deploy operator {noformat}./build/run-openshift.sh{noformat} * change the default number of initial replicas from 2 to 3 {noformat}sed -i 's/2/3/' deploy/crds/quickstart-cr.yaml{noformat} * deploy quickstart project from operator repository {noformat}oc apply -f deploy/crds/quickstart-cr.yaml{noformat} * wait for both replicas to be ready {noformat}oc get pods NAME READY STATUS RESTARTS AGE quickstart-0 1/1 Running 0 31s quickstart-1 1/1 Running 0 31s quickstart-2 1/1 Running 0 31s wildfly-operator-5bcb545b46-j788h 1/1 Running 0 41s{noformat} * scale down to 2 {noformat}oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/replicas", "value":2}]' --type json{noformat} * wait for scale down to perform {noformat} Pods: Name: quickstart-0 Pod IP: 10.128.1.193 State: ACTIVE Name: quickstart-1 Pod IP: 10.128.1.192 State: ACTIVE Replicas: 2 Scalingdown Pods: 0 {noformat} * edit the CRD (e.g. add an env variable) {noformat}oc edit wildflyserver quickstart ... replicas: 2 env: - name: FOO value: BAR{noformat} * wait for both pods to be reloaded * see the [^operator-logs.txt] ** apart WFWIP-251, there are 2 extra error messages There might be other ways to reproduce the issue, but these should make it 100% appearance (at least for me). *actual* Error messages in operator log {noformat} {"level":"error","ts":1571215869.7030337,"logger":"wildlfyserver_resources","msg":"Failed to update resource","WildFlyServer.Namespace":"wildfly-test","WildFlyServer.Name":"quickstart","Resource.Name":"quickstart","Resource.Type":"*v1.StatefulSet","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."} {"level":"error","ts":1571215869.7032435,"logger":"wildflyserver_controller","msg":"Failed to update StatefulSet.","StatefulSet.Namespace":"wildfly-test","StatefulSet.Name":"quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."} {"level":"error","ts":1571215869.7034042,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"wildfly-test/quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."} {noformat} *expected* No error messages in operator log. Operator image build from [0a221ea|https://github.com/wildfly/wildfly-operator/commit/0a221eac5eb462...] -- 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