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

AMQ Broker CR instance cannot be cascade-deleted without graceful shutdown

XMLWordPrintable

    • False
    • None
    • False
    • User Experience
    • +
    • Workaround Exists
    • Hide

      Graceful shutdown the AMQ Broker service before attempting to delete, i.e. set spec.deploymentPlan.size to 0 in the AMQ Broker CR definition.

      Show
      Graceful shutdown the AMQ Broker service before attempting to delete, i.e. set spec.deploymentPlan.size to 0 in the AMQ Broker CR definition.
    • Hide
      • Install the latest AMQ Broker Operator
      • Create an AMQ Broker CR (set spec.deploymentPlan.size to 1)
      • wait for the created pod to be ready
      • cascade delete the CR by calling oc delete activemqartemis ex-aao --cascade=foreground

      The delete call hangs, which is not happening when installing the operator 7.x channel (7.9.z).

      Show
      Install the latest AMQ Broker Operator Create an AMQ Broker CR (set spec.deploymentPlan.size to 1) wait for the created pod to be ready cascade delete the CR by calling oc delete activemqartemis ex-aao --cascade=foreground The delete call hangs, which is not happening when installing the operator 7.x channel (7.9.z).

      A test is installing the latest operator version and creating an AMQ Broker CR with a size of 1 replica.
      Then the test waits for the pod to be ready, before attempting to delete it with a foreground propagation policy.
      This last call is then blocked and the whole deletion process hangs unless the number of replicas is set to 0.
      This looks like a regression from 7.9.z, where the issue doesn't show up.

            gtully@redhat.com Gary Tully
            fburzigo Fabio Burzigotti
            Michal Toth Michal Toth
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: