Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.15.0
-
None
-
3
-
9223372036854775807
Description
This issue was created by maloo for S Buisson <sbuisson@ddn.com>
This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/6dc80157-47d4-4055-9907-0ee99e3974b7
test_101a failed with the following error:
could not map uid 500 to root in namespace
It seems the error is due to 'newuidmap':
== sanity-pcc test 101a: Test auto attach in mount namespace (simulated container) =================== 13:07:40 (1641388060) CMD: onyx-41vm2 cat /proc/sys/user/max_user_namespaces CMD: onyx-41vm2 echo 10 > /proc/sys/user/max_user_namespaces creating user namespace for 500 CMD: onyx-41vm2 runas -u 500 -g 500 unshare -Um sleep 600 CMD: onyx-41vm2 pgrep sleep onyx-41vm2: running as uid/gid/euid/egid 500/500/500/500, groups: onyx-41vm2: [unshare] [-Um] [sleep] [600] Created NS: child (sleep) pid CMD: onyx-41vm2 runas -u 500 -g 500 newuidmap 0 500 1 onyx-41vm2: running as uid/gid/euid/egid 500/500/500/500, groups: onyx-41vm2: [newuidmap] [0] [500] [1] onyx-41vm2: newuidmap: Could not open proc directory for target 0 sanity-pcc test_101a: @@@@@@ FAIL: could not map uid 500 to root in namespace
VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-pcc test_101a - could not map uid 500 to root in namespace