Bug 1939416

Summary:	Mounts failing with error "Failed to setup mount unit: Invalid argument"
Product:	OpenShift Container Platform	Reporter:	Neil Girard <ngirard>
Component:	Storage	Assignee:	Fabio Bertinatto <fbertina>
Storage sub component:	Kubernetes	QA Contact:	Qin Ping <piqin>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	high	CC:	anisal, aos-bugs, bbreard, dtardon, dwalsh, hgomes, imcleod, jligon, jokerman, jsafrane, mbetti, miabbott, nagrawal, naygupta, nchoudhu, ngirard, npaez, nstielau, palshure, pehunt, rphillips, schoudha, shsaxena, systemd-maint-list, tsweeney
Version:	4.6	Keywords:	Reopened, UpcomingSprint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1897337	Environment:
Last Closed:	2021-03-19 14:35:36 UTC	Type:	---
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:	1787148, 1897337
Bug Blocks:	1915520

Comment 1 Neil Girard 2021-03-16 11:37:01 UTC

Hello,

As instructed I've cloned the original defect for my customer's issue with this not being completely fixed in OCP 4.6.17.  From what I can tell, we are no longer seeing the "Failed to start transient scope unit: Argument list too long" being logged, but we still get lots of "Failed to set up mount unit: Invalid argument" with the mounts failing.  A new sosreport from 4.6.17 is attached to the case and can be accessed via supportshell.

Thanks!

Comment 3 Peter Hunt 2021-03-16 14:41:20 UTC

moving back to node until there's evidence this is someone else

Comment 5 Peter Hunt 2021-03-16 14:46:25 UTC

upon inspection, this is looking suspiciously like https://bugzilla.redhat.com/show_bug.cgi?id=1884800, sending over to storage for futher triage

Comment 6 Jan Safranek 2021-03-19 14:35:36 UTC

If you see only "Failed to set up mount unit: Invalid argument", it's really duplicate of bug #1884800. There is not an easy way how to fix it, however, the message is completely harmless. No data is lost, everything is mounted as it should be.

*** This bug has been marked as a duplicate of bug 1884800 ***