Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-21550

Improve services rabbitmq failover behavior when one worker is down

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • rhos-18.0.17 FR 5
    • rhos-18.0.10 FR 3
    • infra-operator
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • rhos-ops-platform-services-pidone
    • None
    • Sprint 9, Sprint 10, Sprint 11, Sprint 12
    • 4
    • Critical

      To Reproduce Steps to reproduce the behavior:

      1. deploy controlplane and dataplane with 3 nodes rabbitmq cluster
      2. abruptly power off one worker where one rabbitmq replica is running
      3. observe nova services (computes and/or other services) impact

      Expected behavior

      • services should fail over to remaining rabbitmq cluster nodes even if a pod is stuck on a dead worker
      •  

              rhn-support-lmiccini Luca Miccini
              rhn-support-lmiccini Luca Miccini
              rhos-dfg-pidone
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: