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.
Description of problem:
A customer was seeing his gfs2 filesystem managed by pacemaker shutting down before pacemaker started the shutdown process when doing a "shutdown -h now". This should not occur if the filesystem is managed by pacemaker.
We should create systemd unit files for filesystems that are considered network filesystems by systemd for our `Filesystem` resource-agent.
Any filesystem that is supported by the `Filesystem` resource-agent that is considered a `network` filesystem by systemd [1] should be include a unit file system to make sure that those filesystem are not shutdown before pacemaker.
Version-Release number of selected component (if applicable):
resource-agents-4.9.0-16.el8.x86_64
How reproducible:
Every time
Steps to Reproduce:
1. Configure a gfs2 filesystem that is managed by pacemaker.
2. Do: shutdown -h now
Actual results:
The gfs2 filesystems managed by pacemaker are shutdown before pacemaker starts the shutdown process.
Expected results:
The gfs2 filesystem should NOT be shutdown by systemd and unmounted. They should only be unmounted when pacemaker begins
its shutdown.
Additional info:
We should add a check on Filesystem type for the 'Filesystem' resource-agent then create a unit file similar to what we do with "LVM-activate" resource. We should do this for any type that "Filesystem" resource-agent supports and which is considered a network filesystem by systemd.
Create the following file:
# touch /etc/systemd/system/resource-agents-deps.target.d/gfs2.conf
Then add the following to the file /etc/systemd/system/resource-agents-deps.target.d/gfs2.conf:
[Unit]
After=remote-fs.target
Then reload systemd
# systemctl daemon-reload
The systemd_drop_in() function can do this. See lvm_start() in LVM-activate.
This would be something like
```
# if this is a remote filesystem (https://github.com/systemd/systemd/blob/v253/src/basic/filesystems.c#L115-L132)
systemd_drop_in "99-Filesystem-remote" "After" \
"remote-fs.target"
```
We should think about whether Wants= or Requires= is also necessary. I think After= is sufficient.
Comment 2Oyvind Albrigtsen
2023-05-17 10:35:07 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 (resource-agents bug fix and enhancement update), 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-2023:6312