Bug 1915520 - Mounts failing with error "Failed to start transient scope unit: Argument list too long"
Summary: Mounts failing with error "Failed to start transient scope unit: Argument lis...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.5.z
Assignee: Peter Hunt
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On: 1884800 1897337 1939416
Blocks: 1915521
TreeView+ depends on / blocked
 
Reported: 2021-01-12 19:43 UTC by OpenShift BugZilla Robot
Modified: 2024-06-13 23:54 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-20 05:49:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github cri-o cri-o pull 4453 0 None closed [1.18] set inactive-or-failed CollectMode if appropriate 2021-02-17 19:49:05 UTC
Red Hat Product Errata RHBA-2021:0033 0 None None None 2021-01-20 05:49:34 UTC

Comment 1 Peter Hunt 2021-01-12 19:45:21 UTC 
fixed in attached PR
Comment 4 Sunil Choudhary 2021-01-14 11:09:08 UTC 
Verified on 4.5.0-0.nightly-2021-01-13-200602. I do not see any mount failure in events or node journal logs.

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.5.0-0.nightly-2021-01-13-200602   True        False         3h14m   Cluster version is 4.5.0-0.nightly-2021-01-13-200602

$ oc get nodes -o wide
NAME                                             STATUS   ROLES    AGE     VERSION           INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                                                       KERNEL-VERSION                 CONTAINER-RUNTIME
qeci-13576-hswr9-m-0.c.openshift-qe.internal     Ready    master   3h50m   v1.18.3+f561b20   10.0.0.95                   Red Hat Enterprise Linux CoreOS 45.82.202101131830-0 (Ootpa)   4.18.0-193.40.1.el8_2.x86_64   cri-o://1.18.4-5.rhaos4.5.gitd655863.el8
qeci-13576-hswr9-m-1.c.openshift-qe.internal     Ready    master   3h50m   v1.18.3+f561b20   10.0.0.53                   Red Hat Enterprise Linux CoreOS 45.82.202101131830-0 (Ootpa)   4.18.0-193.40.1.el8_2.x86_64   cri-o://1.18.4-5.rhaos4.5.gitd655863.el8
qeci-13576-hswr9-m-2.c.openshift-qe.internal     Ready    master   3h50m   v1.18.3+f561b20   10.0.0.96                   Red Hat Enterprise Linux CoreOS 45.82.202101131830-0 (Ootpa)   4.18.0-193.40.1.el8_2.x86_64   cri-o://1.18.4-5.rhaos4.5.gitd655863.el8
qeci-13576-hswr9-w-a-0.c.openshift-qe.internal   Ready    worker   3h23m   v1.18.3+f561b20   10.0.32.21                  Red Hat Enterprise Linux CoreOS 45.82.202101131830-0 (Ootpa)   4.18.0-193.40.1.el8_2.x86_64   cri-o://1.18.4-5.rhaos4.5.gitd655863.el8
qeci-13576-hswr9-w-b-1.c.openshift-qe.internal   Ready    worker   3h22m   v1.18.3+f561b20   10.0.32.37                  Red Hat Enterprise Linux CoreOS 45.82.202101131830-0 (Ootpa)   4.18.0-193.40.1.el8_2.x86_64   cri-o://1.18.4-5.rhaos4.5.gitd655863.el8


$ oc get events -A | grep -i "Argument list too long"
$ 

$ oc get events -A | grep -i "mount failed: exit status 1"
$

$ oc debug node/qeci-13576-hswr9-w-a-0.c.openshift-qe.internal
Starting pod/qeci-13576-hswr9-w-a-0copenshift-qeinternal-debug ...
To use host binaries, run `chroot /host`
...

sh-4.4# journalctl | grep -i "Failed to set up mount unit: Invalid argument"
sh-4.4# 

sh-4.4# journalctl | grep -i "Failed to set up mount unit"
sh-4.4# 

sh-4.4# journalctl | grep -i "Argument list too long"
sh-4.4#
Comment 6 errata-xmlrpc 2021-01-20 05:49:29 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 (OpenShift Container Platform 4.5.27 bug fix 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-2021:0033
Note You need to log in before you can comment on or make changes to this bug.