Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-41848

Deleting a failed node to trigger virtual machine failover points to MHC, instead of NHC

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • ---
    • ---
    • No

      Description of problem:

      We want to guide our users to use NHC, not MHC .
      

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

      4.16
      

      Steps to Reproduce:

      1. Read https://docs.openshift.com/container-platform/4.15/virt/nodes/virt-triggering-vm-failover-resolving-failed-node.html#virt-triggering-vm-failover-resolving-failed-node
      2.
      3.
      

      Actual results:
      If a node fails and machine <https://docs.openshift.com/container-platform/4.15/machine_management/deploying-machine-health-checks.html#machine-health-checks-about_deploying-machine-health-checks> health checks are not deployed on your cluster, virtual machines (VMs) with runStrategy: Always configured are not automatically relocated to healthy nodes. To trigger VM failover, you must manually delete the Node object.

      Expected results:
      If a node fails and node <https://access.redhat.com/articles/7057929> health checks are not deployed on your cluster, virtual machines (VMs) with runStrategy: Always configured are not automatically relocated to healthy nodes. To trigger VM failover, you must manually delete the Node object.

      Additional info:

      
      

              rhn-support-sjess Sabrina Jess
              dholler@redhat.com Dominik Holler
              Geetika Kapoor Geetika Kapoor
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: