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.
DescriptionFabio Massimo Di Nitto
2013-11-25 14:06:28 UTC
Description of problem:
This bug is intended to track all bugs encountered in HA nfs-server deployment scenario testing for RHEL 7.
Testplan: TBA
Draft of HA nfs-server deployment scenario:
http://rhel-ha.etherpad.corp.redhat.com/PRD-HA-nfsserver
The scenario can be tested _without_ locks and works correctly in the following
scenarios:
Basic operations, including the following steps:
* create shared lvm
* setup cluster
* setup hanfs group
* check that the following action are possible and verify that they has
been performed correctly: start, stop, move, destroy
Failover operations, including tho following on node running hanfs:
1/ node suddenly fails
2/ its network becomes inavailable
3/ switch fails (nodes sudenly stops seing each other)
link to tests in internal qe-beaker:
https://url.corp.redhat.com/cluster-qe-beaker-nfsserver-ap-nolocks-01
----
The same tests could not have been done with locking of the files turned on because of the following bug:
[https://bugzilla.redhat.com/show_bug.cgi?id=1120850] unable recover NFSv3 locks NLM_DENIED_NOLOCK
bz1159234 is now the blocker of the scenario tests as described in its comment 10.
Summary: /var/lib/nfs is not correctly umounted due to the change in systemd units that does not require it anymore. It prevents stopping of the volume group group and the node is restarted.