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.
Bug 1940973 - longer mount points cause systemd invalid argument messages
Summary: longer mount points cause systemd invalid argument messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: David Tardon
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
: 2155314 (view as bug list)
Depends On:
Blocks: 2094712 2094714
TreeView+ depends on / blocked
 
Reported: 2021-03-19 16:55 UTC by Hemant Kumar
Modified: 2024-12-20 19:46 UTC (History)
11 users (show)

Fixed In Version: systemd-239-61.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2094712 2094714 (view as bug list)
Environment:
Last Closed: 2022-11-08 10:49:17 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github redhat-plumbers systemd-rhel8 pull 269 0 None open Handle mount/device units with long paths 2022-05-10 08:49:14 UTC
Github systemd systemd issues 18077 0 None closed RFE: support for long unit names 2022-05-09 13:40:50 UTC
Red Hat Product Errata RHBA-2022:7727 0 None None None 2022-11-08 10:49:44 UTC

Description Hemant Kumar 2021-03-19 16:55:03 UTC 
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.
Comment 1 Hemant Kumar 2021-03-19 16:56:42 UTC 
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.
Comment 4 Michal Sekletar 2021-12-20 16:28:45 UTC 
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/15911
https://github.com/systemd/systemd/pull/19801
Comment 5 David Tardon 2022-05-10 11:35:29 UTC 
If anyone wants to try this, I've uploaded test rpms at https://people.redhat.com/dtardon/systemd/bz1940973-long-unit-names/ .
Comment 12 Plumber Bot 2022-07-07 14:27:47 UTC 
fix merged to github master branch -> https://github.com/redhat-plumbers/systemd-rhel8/pull/269
Comment 23 errata-xmlrpc 2022-11-08 10:49:17 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 (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
Comment 24 David Tardon 2023-01-05 14:01:38 UTC 
*** Bug 2155314 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.