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 1052613[details]
Patch with the changes needed to allow the cluster to deal correctly with NFS mount resources
Description of problem:
With pacemaker pacemaker-1.1.12 (22.el7_1.2) the pacemaker init script doesn't wait to have a proper network connection before coming up, and this drive the failure of NFS mount resources.
This is particularly visible and disappointing when deploying OpenStack via osp-installer and choosing NFS.
Version-Release number of selected component (if applicable):
pacemaker-1.1.12-22.el7_1.2.x86_64
How reproducible:
Always
Steps to Reproduce:
1. add a NFS resource ocf::heartbeat:Filesystem
2. reboot one or all the nodes
Actual results:
When the cluster is up, the NFS resource will be disabled
Expected results:
The cluster wait to be online and then turn start all resources
Additional info:
Attached you can find a patch produced by Matteo Bernacchi that fix the pacemaker misbehaviour.
Comment on attachment 1052752[details]
systemd service.unit patch to allow the cluster to deal correctly with NFS mount resources
Pacemaker doesn't require either of these items.
The NFS unit or agent should be dealing with this.
Possibly something for the resource agent to take care of
Comment 14Oyvind Albrigtsen
2016-01-21 09:42:27 UTC
(In reply to Andrea Perotti from comment #8)
> I agree, it's a workaround for our specific problem.
>
> I've found this
Can you confirm whether this is still an issue or not with the fixed rpcbind version in RHEL7.2 from: https://bugzilla.redhat.com/show_bug.cgi?id=1203820?
Created attachment 1052613 [details] Patch with the changes needed to allow the cluster to deal correctly with NFS mount resources Description of problem: With pacemaker pacemaker-1.1.12 (22.el7_1.2) the pacemaker init script doesn't wait to have a proper network connection before coming up, and this drive the failure of NFS mount resources. This is particularly visible and disappointing when deploying OpenStack via osp-installer and choosing NFS. Version-Release number of selected component (if applicable): pacemaker-1.1.12-22.el7_1.2.x86_64 How reproducible: Always Steps to Reproduce: 1. add a NFS resource ocf::heartbeat:Filesystem 2. reboot one or all the nodes Actual results: When the cluster is up, the NFS resource will be disabled Expected results: The cluster wait to be online and then turn start all resources Additional info: Attached you can find a patch produced by Matteo Bernacchi that fix the pacemaker misbehaviour.