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

Changes in AmqSecurity CR doesn't trigger broker restart.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • AMQ 7.9.0.CR2
    • operator
    • None
    • False
    • False
    • Hide

      1) oc create -f amq_security.yaml

      2) oc create -f amq_broker_resource.yaml

      3) At this point, settings from 1) should have been applied. Verify.

       

      4) Change security settings then do oc apply -f amq_security_changed.yaml

      5) At this point, broker pod doesn't restart and changes to amqsecurity instance don't get propagated into the pod.

      Show
      1) oc create -f amq_security.yaml 2) oc create -f amq_broker_resource.yaml 3) At this point, settings from 1) should have been applied. Verify.   4) Change security settings then do oc apply -f amq_security_changed.yaml 5) At this point, broker pod doesn't restart and changes to amqsecurity instance don't get propagated into the pod.

      Changes in amqsecurity resource do not trigger change in broker's configuration and poddoesn't restart after change has been introduced.

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

              Created:
              Updated:
              Resolved: