Bug 1940973

Summary:	longer mount points cause systemd invalid argument messages
Product:	Red Hat Enterprise Linux 8	Reporter:	Hemant Kumar <hekumar>
Component:	systemd	Assignee:	David Tardon <dtardon>
Status:	CLOSED ERRATA	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	8.0	CC:	abetkike, apizarro, chris.bowles, dtardon, fkrska, msekleta, msoares, rpinto, sbelmasg, ssonigra, systemd-maint-list
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	systemd-239-61.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2094712 2094714 (view as bug list)		Environment:
Last Closed:	2022-11-08 10:49:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2094712, 2094714

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. ***