[jboss-jira] [JBoss JIRA] (WFWIP-182) OCP4 Operator doesn't react on env update

[Petr Kremensky (Jira)]

Petr Kremensky created WFWIP-182:
------------------------------------

             Summary: OCP4 Operator doesn't react on env update
                 Key: WFWIP-182
                 URL: https://issues.jboss.org/browse/WFWIP-182
             Project: WildFly WIP
          Issue Type: Bug
          Components: OpenShift
            Reporter: Petr Kremensky
            Assignee: Brian Stansberry


Updating env in WildFlyServerSpec is not reflected by Operator. The issue is specific to OCP4 (works fine on OCP3).

Operator image build from https://github.com/wildfly/wildfly-operator/commit/467407a6c21102c77d95e9a4c7b6ab6bcc896e49
*OpenShift Version:* 4.1.9

**Actual:**

 * update of env do nothing with the statefulset configuration - no change on Wildfly pods

**Expected:**

 * update of env create a new generation of statefulset and trigger rolling update of Wildfly pods

Deploy the application using wildfly operator
{code}
$ cat wildfly-operator.yaml
apiVersion: wildfly.org/v1alpha1
kind: WildFlyServer
metadata:
  name: wildfly-operator
spec:
  applicationImage: "quay.io/wildfly/wildfly-centos7:17.0"
  env:
    - name: TEST_START
      value: INITIAL
  size: 1
{code}
Deploy and see the envs
{code}
oc apply -f wildfly-operator.yaml
oc set env pod/wildfly-operator-0 --list | grep TEST
TEST_START=INITIAL
{code}

Use oc client to edit the env (e.g. modify the env key & value)
{code}
oc edit wildflyserver wildfly-operator
  env:
  - name: TEST_UPDATE
    value: UPDATE
{code}
Notice a new generation of operator is created, {color:red}but no new generation of statefulset{color} - no update to pods.
{code}
$ oc get wildflyserver wildfly-operator -o yaml | grep generation
  generation: 2
$ oc get statefulset.apps/wildfly-operator -o yaml | grep generation
  generation: 1
$ oc set env pod/wildfly-operator-0 --list | grep TEST
TEST_START=INITIAL
{code}



--
This message was sent by Atlassian Jira
(v7.13.5#713005)