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

The Operator shows forbidden errors when you deploy a CR and message migration does not work as expected

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • AMQ 7.12.0.OPR.1.GA
    • operator
    • None
    • False
    • None
    • False
    • Hide

      To reproduce the issue, change the attached reporducer.yaml to watch a namespace which is not the operator namespace and deploy it.

      After the operator is running, deploy a simple broker CR.

      Show
      To reproduce the issue, change the attached reporducer.yaml to watch a namespace which is not the operator namespace and deploy it. After the operator is running, deploy a simple broker CR.
    • Important

      When an Operator that is installed using the CLI thru OperatorHub and watches multiple namespaces, an error is displayed when you deploy a CR and message migration does not work as expected.

      Also after some more investigation, there is a issue on message migration when multiple namespace watch is used. In a scenario with 2 broker nodes after the scaledown, the messages from the node which were removed are not migrated to remaining node and are lost.

       

        1. logs.zip
          33.35 MB
        2. reproducer.yml
          0.6 kB

              gaohoward Howard Gao
              tbueno@redhat.com Tiago Bueno
              Tiago Bueno Tiago Bueno
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: