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

TNF: initializating podman-etcd with meta causes OCF_RESKEY_CRM_meta_notify to be set to false

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.19.0
    • 4.19
    • Two Node Fencing
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-55111. The following is the description of the original issue:
      —
      Description of problem:

      See this line: https://github.com/openshift/cluster-etcd-operator/blob/main/pkg/tnf/pkg/pcs/etcd.go#L25

      For some reason, possibly a bug in pacemaker, initializing the podman-etcd resource agent in with `meta notify=true` doesn't set the OCF_RESKEY_CRM_meta_notify flag like it's supposed to.

In our testing, it has been possible to override this this by omitting "meta" in the resource creation step.

      How reproducible:

      Run the graceful recovery test on a TNF cluster.
OR
Run `crm_mon --as-xml` on one of the CP nodes

      Steps to Reproduce:

      1. Deploy a TNF cluster
2. Try to recover from graceful shutdown
3. Cluster doesn't recover, so observe the logs in the CP node

      Actual results:

      Cluster doesn't recover

      Expected results:

      Cluster recovers

      Additional info:

      None

              rh-ee-clobrano Carlo Lobrano
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Douglas Hensel Douglas Hensel
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: