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.
Bug 1628966 - ordering constraints and resource failures
Summary: ordering constraints and resource failures
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: 7.7
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-14 14:24 UTC by Devin Bougie
Modified: 2019-08-06 12:54 UTC (History)
4 users (show)

Fixed In Version: pacemaker-1.1.20-1.el7
Doc Type: Bug Fix
Doc Text:
Cause: Pacemaker ignored asymmetric start-B-after-A ordering constraints when B was already started. Consequence: If B needed to restart while A was stopped, B would be allowed to start. Fix: Pacemaker respects asymmetric start-B-after-A ordering constraints even if B is already started to begin with. Result: If B needs to restart while A is stopped, B will stop but not be allowed to start.
Clone Of:
Environment:
Last Closed: 2019-08-06 12:53:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Cluster Labs 5364 0 None None None 2018-09-14 14:24:08 UTC
Red Hat Product Errata RHBA-2019:2129 0 None None None 2019-08-06 12:54:11 UTC

Description Devin Bougie 2018-09-14 14:24:08 UTC 
Description of problem:
There is a bug in the pacemaker scheduler that allows a resource to be restarted even if a resource it is dependent on is not started.  Please see https://bugs.clusterlabs.org/show_bug.cgi?id=5364

This has been fixed in the master branch (for 2.0.1 release) by commit 043b9f7, which will also be backported for the 1.1.20 release.  We would love to see this back ported to RHEL7.

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

How reproducible:
Always

Steps to Reproduce:
For example, our desired behavior is as follows:
- only start resource B if resource A is already running.
- if both resources are running and resource A stops, continue running resource B (a non-symmetrical ordering constraint)
- if resource B fails and resource A is disabled, resource B should not restart until resource A is started

Everything works properly, except when resource B fails when resource A is disabled and stopped.  When this happens, pacemaker recovers and restarts resource B even though resource A is stopped.

Here are our example resources and constraints:
------
 Resource: sleep_a (class=ocf provider=classe type=anything)
  Attributes: binfile=/usr/bin/sleep cmdline_options=infinity
  Operations: monitor interval=10 timeout=20s (sleep_a-monitor-interval-10)
              start interval=0s timeout=20s (sleep_a-start-interval-0s)
              stop interval=0s on-fail=block (sleep_a-stop-interval-0s)

 Resource: sleep_b (class=ocf provider=classe type=anything)
  Attributes: binfile=/usr/bin/sleep cmdline_options=infinity
  Operations: monitor interval=10 timeout=20s (sleep_b-monitor-interval-10)
              start interval=0s timeout=20s (sleep_b-start-interval-0s)
              stop interval=0s on-fail=block (sleep_b-stop-interval-0s)

  start sleep_a then start sleep_b (kind:Mandatory) (non-symmetrical) (id:ordersleep_a-sleep_b-mandatory)
------

Actual results:
Pacemaker recovers and restarts resource B even though resource A is stopped.

Expected results:
Pacemaker should not recover or restart resource B until resource A is started.

Additional info:
https://bugs.clusterlabs.org/show_bug.cgi?id=5364
Comment 2 Ken Gaillot 2018-09-14 17:41:19 UTC 
This fix is expected to land in 7.7. If the issue is more urgent, we can ask for a 7.6.z-stream.
Comment 3 Patrik Hagara 2019-03-20 11:15:21 UTC 
qa-ack+

reproducer in bug comment#0
Comment 7 errata-xmlrpc 2019-08-06 12:53:44 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2129
Note You need to log in before you can comment on or make changes to this bug.