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:
Mount a volume that is named in such a way that after systemd-escape, its name becomes greather than 256 characters.
This causes endless messages in journal logs:
Failed to set up mount unit: Invalid argument
Expected results:
systemd should support mount points bigger than 256 chars - https://github.com/systemd/systemd/pull/14294
Additional info:
Additionally the log line should - at very minimum log which mount point is problematic.
Corresponding Openshift BZ - https://bugzilla.redhat.com/show_bug.cgi?id=1884800
Without fixing this in systemd we are left with either documenting this as limitation or asking customers to fix their datastore/path names in such a way that systemd could accept them. Fixing this in Openshift/k8s is basically whack-a-mole problem.
So far consensus upstream was that systemd shouldn't be disturbed by overly long mount or sysfs device names, i.e. it shouldn't misbehave or excessively log about the fact. Situation should be noted in the log and systemd should carry on, the only other result is that such unit won't be created and hence you wouldn't be able to manage such mount or device as systemd unit.
To fix this issue (to the extent described above) we need to backport patches from following PRs,
https://github.com/systemd/systemd/pull/15911https://github.com/systemd/systemd/pull/19801
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 (systemd 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-2022:7727