Uploaded image for project: 'Red Hat Workload Availability'
  1. Red Hat Workload Availability
  2. RHWA-278

[MHC] SNR CR not deleted when triggered by MHC

XMLWordPrintable

    • False
    • False
    • not required because MHC support is a PoC only
    • Release Note Not Required
    • Proposed

      Test case OCP-69964 Fails in with SNR 0.9.0 (Tested in OCP 4.16).
      This TC configures MHC instances for workers and control planes, triggering the remediations via SNR and also Metal3Remediation.

      After the nodes are remediated, the Metal3Remediation CR is deleted, but the SNR CR is not, leaving the node tainted by the SNR instance. See attached yaml files for configurations active when the SNR CR is present and no longer needed as the node is recovered already.

      The TC is passing in SNR 0.8.0 

       

        1. clusterserviceversion-self-node-remediation.v0.9.0.yaml
          54 kB
        2. machinehealthcheck-mhc-snr-master.yaml
          2 kB
        3. mhc_snr_4_18_disconnected_12_sept.text
          22 kB
        4. node-master-0-0.yaml
          14 kB
        5. selfnoderemediation-ocp-edge-cluster-0-tvkcj-master-0lq2qt.yaml
          3 kB
        6. selfnoderemediationtemplate-selfnoderemediationtemplate-sample.yaml
          1 kB

              mshitrit@redhat.com Michael Shitrit
              frmoreno Francisco Javier Moreno Moreno
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: