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

AMQ Broker Drainer pod doesn't function properly after changing MessageMigration in CR

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • AMQ 7.11.0.OPR.1.GA
    • operator
    • False
    • None
    • False

      1. Create AMQ Broker installation using cr_initial.yaml
      2. update it into cr_step1.yaml
      3. update it into cr_step2.yaml
      4. Observe drainer pod which keeps crashing

      Changes between crs:

      1) initially, MessageMigration is turned on. Otherwise its a default CR of size 2.
      2) Step1 is to disable MessageMigration.
      3) Step2 is to scale the CR down to 1 instance of Broker.

      Similar thing is happening to the opposite situation, i.e. :

      1. No MM
      2. Enable MM

      In this case, Drainer pod starts and puts this in event log:

      61s         Warning   FailedMount              pod/sd-broker-ss-1                                   Unable to attach or mount volumes: unmounted volumes=[sd-broker], unattached volumes=[sd-broker kube-api-access-pmjsr]: timed out waiting for the condition

      What seems to be happening is, PVC is not removed after scaledown event, so that Drainer cant' attach it's PV.

        1. cr_initial.yaml
          0.2 kB
        2. cr_step1.yaml
          0.2 kB
        3. cr_step2.yaml
          0.2 kB

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

              Created:
              Updated: