Bug 1924502 - Failed to start transient scope unit: Argument list too long / systemd[1]: Failed to set up mount unit: Invalid argument
Summary: Failed to start transient scope unit: Argument list too long / systemd[1]: Fa...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.8.0
Assignee: Peter Hunt
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-03 07:23 UTC by Nelson Lombo Paez
Modified: 2024-12-20 19:35 UTC (History)
25 users (show)

Fixed In Version: 4.5.33, 4.6.21, 4.7.1
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-27 22:38:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github cri-o cri-o pull 4563 0 None closed config/node: refactor checking for CollectMode 2021-02-16 16:21:56 UTC
Red Hat Knowledge Base (Solution) 4620671 0 None None None 2021-05-14 14:25:10 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:40:41 UTC

Description Nelson Lombo Paez 2021-02-03 07:23:18 UTC
Description of problem:

There is a Bugzilla open to a similar issue but regarding RHEL7 (https://bugzilla.redhat.com/show_bug.cgi?id=1787148) and this one regarding OpenShift 4.4 (https://bugzilla.redhat.com/show_bug.cgi?id=1897337) the last one it was suppose to be fixed in version 4.6.12 (https://access.redhat.com/errata/RHSA-2021:0037) but I have a customer with the same issue in version 4.6.12.

Some pods get stuck with the following logs[1]:


Also, it's not possible to create a sosreport for the following logs[2]

Attached the mustgather[3]

Please, let me know if you need anything else from my side

Comment 4 Peter Hunt 2021-02-10 20:26:21 UTC
upstream PR to fix this, will backport to 4.6 and 4.5 once merged

Comment 6 Peter Hunt 2021-02-11 14:21:43 UTC
sure! It was added to the links, but here it is a comment github.com/cri-o/cri-o/pull/4563 :)

Comment 7 Peter Hunt 2021-02-12 19:07:58 UTC
1.21 (4.8) version merged. Backports for 4.5-4.7 are in progress

Comment 19 Sunil Choudhary 2021-03-31 07:19:19 UTC
Checked this on nightly build release:4.8.0-0.nightly-2021-03-26-054333 with multiple clusters and kept them running for couple of days. I did not see this failure on them.

Comment 31 Peter Hunt 2021-05-24 20:37:29 UTC
this bug should be fixed for most cases where we previously got the "Argument list too long" error message in systemd 

If that issue is still present, I will need the sos_report from the nodes *from the time the issue is happening*. you can also get must-gather, but note must-gather only gathers from the masters by default. I need it from the node that is affected or I cannot help.

If systemd is failing for another reason ("Invalid argument" that isn't followed by "Argument list too long") then I recommend opening a new bug, as that would be something different.

Re: comment#25: I cannot glean what is going wrong because I only have a must-gather from the masters, not a sos_report from the affected node. please attach the sos_report or must-gather from the correct node for me to continue.

sorry for the silence folks, my BZ filtering mechanism doesn't keep VERIFIED bugs on my radar, so these questions kept slipping. If you need my attention, setting needsinfo would be helpful to me.

Comment 39 errata-xmlrpc 2021-07-27 22:38:32 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security 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/RHSA-2021:2438

Comment 48 Red Hat Bugzilla 2023-09-15 01:00:23 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


Note You need to log in before you can comment on or make changes to this bug.