Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-13558

LVMS: After node loss, lvmCluster resource still has the entry for the lost node

XMLWordPrintable

    • No
    • 2
    • OCP VE Sprint 240, OCP VE Sprint 241, OCP VE Sprint 242, OCP VE Sprint 243, OCP VE Sprint 244
    • 5
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • LVMS now can properly handle loss of worker nodes in SNO+worker Node configurations.
    • Bug Fix
    • In Progress

      Description of problem:

      After additional worker node loss, lvmCluster still has the entry for lost node and lvmCluster state remains in "Progressing"

      Version-Release number of selected component (if applicable):

       

      How reproducible:

      Always

      Steps to Reproduce:

      1. Setup LVMS on SNO with additional worker node
2. Remove one of the additioanl worker node
3. LvmCluster resource still shows the entry for lost node and state is in "Progressing"

      Actual results:

       

      Expected results:

      Lost node entry should be removed from lvmCluster and lvmCLuster should be in Active status

      Additional info:

       

            rh-ee-jmoller Jakob Moeller
            rh-ee-rdeore Rahul Deore
            Rahul Deore Rahul Deore
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: