Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 908450[details]
reproducer script
Description of problem:
Creating non-set resources constraints 'order a then b' and 'colocation a with
b' runs all the resources as expected where replacing the same constraints with
'order set a b' 'colocation set a b' stops some of the resources.
Version-Release number of selected component (if applicable):
pcs-0.9.115-32.el7.x86_64
pacemaker-1.1.10-29.el7.x86_64
How reproducible: always
Steps to Reproduce:
1. get attached c.sh
2. ./c.sh create_resources
3. ./c.sh set
Actual results: nfsserver and export-1, export-2 stopped
Expected results: all resources running
Additional info:
You can run the same constraints create using no-set 'order a then b' and
'colocation a with b' using the same script:
$ ./c.sh removec #remove constraints
$ ./c.sh noset #create noset constraints
This scenario is a reallife nfs activ-active scenario only the resources are
replaced with dummy resources, the names of the resources are the same.
Here's your problem:
pcs constraint colocation set fs1 nfsserver-clone
is not the equivalent of:
pcs constraint colocation add fs1 with nfsserver-clone
Colocation sets have the same semantics as groups.
See:
http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-sets-collocation.html
What you really wanted was:
pcs constraint colocation set nfsserver-clone fs1
And if you want to use sets, don't use them in pairs, that defeats the purpose :)
Try:
pcs constraint colocation set nfsserver-clone fs1 export1
pcs constraint order set fs1 nfsserver-clone export1
Thanks for the explanation -- I have missed the fact that the somantic of the sets and groups is the same especially that the order of resources needs to be reversed for the sets.
The provided scenario works as as expected when constraints with sets use reversed order than in the provided reproducer.
I'll close the bug with NOTABUG.
Created attachment 908450 [details] reproducer script Description of problem: Creating non-set resources constraints 'order a then b' and 'colocation a with b' runs all the resources as expected where replacing the same constraints with 'order set a b' 'colocation set a b' stops some of the resources. Version-Release number of selected component (if applicable): pcs-0.9.115-32.el7.x86_64 pacemaker-1.1.10-29.el7.x86_64 How reproducible: always Steps to Reproduce: 1. get attached c.sh 2. ./c.sh create_resources 3. ./c.sh set Actual results: nfsserver and export-1, export-2 stopped Expected results: all resources running Additional info: You can run the same constraints create using no-set 'order a then b' and 'colocation a with b' using the same script: $ ./c.sh removec #remove constraints $ ./c.sh noset #create noset constraints This scenario is a reallife nfs activ-active scenario only the resources are replaced with dummy resources, the names of the resources are the same.