RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Orphaned Container Resources  (container resources deleted from the CIB before being stopped) can cause invalid pacemaker transition and resource failures.

How reproducible:

50% of the time. This can be completely random.  Basically if we get lucky, the resources within the orphaned container get stopped before the container is shut down, but there is nothing in the policy engine that strictly enforces this to happen in the correct order.

Steps to Reproduce:
1. create a Container resource.
2. place resources within the container.
3. delete container resource from cib.

Actual results:

The container resource might get torn down before the resources within it, which will cause resources to fail when they shouldn't.... This entire problem occurs because it is impossible to stop a resource living within the container after the container is stopped.  The policy engine must enforce the correct order during container shutdown.

Expected results:

Orphaned container resources are not stopped until all the resources running within them are stopped first.

Additional info:

This has already been fixed upstream. These 3 upstream patches are required to resolve this.

https://github.com/davidvossel/pacemaker/commit/8b5ea1957e3281fa18940f4beb496482948f9dca

https://github.com/davidvossel/pacemaker/commit/015f12fabd4d286add6b7e711108bf235485b552

https://github.com/davidvossel/pacemaker/commit/65ef2c7d8d931a149db3cf8be41225410a27e182

I have verified that the resource residing inside the container is correctly
relocated when container is removed.

duck-03# rpm -q resource-agents
resource-agents-3.9.5-26.el7.x86_64

duck-03# pcs status
...
Online: [ duck-03 ]
Containers: [ duck-03-node01:R-duck-03-node01-lxc ]

Full list of resources:

 virt-fencing   (stonith:fence_ipmilan):        Started duck-03 
 le-dummy       (ocf::heartbeat:Dummy): Started duck-03-node01 
 R-duck-03-node01-lxc   (ocf::heartbeat:VirtualDomain): Started duck-03 
...

duck-03# pcs resource delete R-duck-03-node01-lxc
Removing Constraint - location-R-duck-03-node01-lxc-duck-03-INFINITY
Attempting to stop: R-duck-03-node01-lxc...Stopped
Deleting Resource - R-duck-03-node01-lxc

duck-03# pcs status
...
Online: [ duck-03 ]

Full list of resources:

 virt-fencing   (stonith:fence_ipmilan):        Started duck-03 
 le-dummy       (ocf::heartbeat:Dummy): Started duck-03

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.