Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-5689

Operator cannot handle patching console to ssl Enabled

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • AMQ 7.9.0.CR6
    • operator
    • False
    • False
    • Hide
      Verified on registry-proxy.engineering.redhat.com/rh-osbs/amq7-amq-broker-rhel8-operator:7.9-7 / registry-proxy.engineering.redhat.com/rh-osbs/amq-broker-7-amq-broker-79-openshift-rhel8:7.9-12


      works as expected when patch is applied through one oc operation.
      Show
      Verified on registry-proxy.engineering.redhat.com/rh-osbs/amq7-amq-broker-rhel8-operator:7.9-7 / registry-proxy.engineering.redhat.com/rh-osbs/amq-broker-7-amq-broker-79-openshift-rhel8:7.9-12 works as expected when patch is applied through one oc operation.

    Description

      When user deploys a broker with console exposed but no ssl:

      apiVersion: broker.amq.io/v2alpha5
      kind: ActiveMQArtemis
      metadata:
        name: amq7-critical-dev-aao
        namespace: testsslconsole79
      spec:
        console:
          expose: true
      ...
      

      and then patch it to be sslEnabled:

      oc patch activemqartemis --type merge $BROKER_NAME -p '{"spec":{"console":{"sslEnabled":true,"sslSecret":"my-tls-secret"}}}'
      

       The broker pod will be in failure state because of the new config didn't get processed properly.

       

       

      Attachments

        Issue Links

          Activity

            People

              gaohoward Howard Gao
              gaohoward Howard Gao
              Mikhail Krutov Mikhail Krutov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: