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.
DescriptionStrahil Nikolov
2018-06-13 06:49:26 UTC
Created attachment 1450803[details]
systemd mount and automount unit files with journalctl output
Description of problem:
There are 2 systemd automount units which work inconsistently. Starting manually the automounter works , but once the automount timeouts and umounts the mount point - it never works again.
"Not an absolute path, ignoring : ..."
The mount and automount units are named as per the man pages.
Version-Release number of selected component (if applicable):
systemd-219-57.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1.Create a mount point like: /var/jail/var/lib/libvirt and /var/jail/var/run/libvirt
2.Create mount and automount units as per attachments
3.Start and enable the automount services
Actual results:
When the timeout hits , following access requests are not allowed and the mount point "hangs"
Expected results:
Automounting to be working before and after the timeout hits.
Additional info:
journalctl output is attached in the zip
(In reply to Strahil Nikolov from comment #0)
> "Not an absolute path, ignoring : ..."
This is because the path in the Where directive in the .automount files is enclosed in quotes. Remove them and the warning will disappear. After that, you'll discover the real error: you want an .automount unit for /var/jail/var/lib/libvirt, but the Where path is /var/lib/libvirt.
Created attachment 1450803 [details] systemd mount and automount unit files with journalctl output Description of problem: There are 2 systemd automount units which work inconsistently. Starting manually the automounter works , but once the automount timeouts and umounts the mount point - it never works again. "Not an absolute path, ignoring : ..." The mount and automount units are named as per the man pages. Version-Release number of selected component (if applicable): systemd-219-57.el7.x86_64 How reproducible: Always Steps to Reproduce: 1.Create a mount point like: /var/jail/var/lib/libvirt and /var/jail/var/run/libvirt 2.Create mount and automount units as per attachments 3.Start and enable the automount services Actual results: When the timeout hits , following access requests are not allowed and the mount point "hangs" Expected results: Automounting to be working before and after the timeout hits. Additional info: journalctl output is attached in the zip