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

cinder:verify openstackcontrolplane replica count reflect reality in openstack services

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • cinder-operator
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • ?
    • ?
    • None
    • Low

      As services now reside on pods, if pod get removed services should be removed fromĀ  component service list.

      1. pods should decrease immediately
        > happening as expected
      2. service status should get down and service should get delete from volume service list
        > service did not get removed from volume service list even after waiting for more then 5 mins.

      Steps to reproduce:
      1 - find out number of pods running for cinder-scheduler, backup
      2 - check for respective pods number
      3 - increase replica value for cinder-schedulerĀ  # oc edit openstackcontrolplane
      4 - verify if changes are reflected and number of pods increased
      5 - verify service list, if new node for service added with up status
      6 - decrease cinder-scheduler replica count in controlplane
      7 - verify pods count and service status and node count in service list

      Both pods and service (in service list) should be decreased.

              geguileo@redhat.com Gorka Eguileor
              rh-ee-auniyal Amit Uniyal
              rhos-dfg-storage-squad-cinder
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: