Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(regression in master) not ok 117 update devices [minimal transition rules] #3014

Closed
kolyshkin opened this issue Jun 9, 2021 · 6 comments · Fixed by #3019
Closed

(regression in master) not ok 117 update devices [minimal transition rules] #3014

kolyshkin opened this issue Jun 9, 2021 · 6 comments · Fixed by #3019

Comments

@kolyshkin
Copy link
Contributor

kolyshkin commented Jun 9, 2021

Got an error from CI for PR #3011, during test (1.16.x) integration test with systemd. Also reproducible on master and other recent PRs.

Quoting https://github.com/opencontainers/runc/runs/2787163520?check_suite_focus=true:

not ok 117 update devices [minimal transition rules]
# (in test file tests/integration/update.bats, line 625)
#   `[ -z "$(<"$CONTAINER_OUTPUT")" ]' failed
# runc spec (status=0):
# 
# runc run -d --console-socket /tmp/bats-run-25456/runc-tmp-recvtty.9wbHaU/console.sock test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# sh: can't create /dev/null: Operation not permitted
# /tmp/bats-run-25456/bats.37480.src: line 603: 39193 Killed                  ( "$RECVTTY" --no-stdin --pid-file "$TMP_RECVTTY_PID" --mode single "$TMP_CONSOLE_SOCKET" &> "$CONTAINER_OUTPUT" )

The test case was added in commit 4438eaa, PR #2391.

This sh: can't create /dev/null: Operation not permitted means somewhere during runc update the device access list might become empty for some time.

May be related to recent PR #2994 (although I do not see how). Definitely not related to PR #2986 as we have cgroup v1 here.

@kolyshkin
Copy link
Contributor Author

Got it again on the same PR, the only difference is go version (1.15 this time). Hmm, maybe it is related to the changes I made in #3011.

From https://github.com/opencontainers/runc/runs/2787301089?check_suite_focus=true:

not ok 117 update devices [minimal transition rules]
# (in test file tests/integration/update.bats, line 625)
#   `[ -z "$(<"$CONTAINER_OUTPUT")" ]' failed
# runc spec (status=0):
# 
# runc run -d --console-socket /tmp/bats-run-25864/runc-tmp-recvtty.5CVnWw/console.sock test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# runc update --pids-limit 30 test_update (status=0):
# 
# sh: can't create /dev/null: Operation not permitted
# /tmp/bats-run-25864/bats.38040.src: line 603: 39758 Killed                  ( "$RECVTTY" --no-stdin --pid-file "$TMP_RECVTTY_PID" --mode single "$TMP_CONSOLE_SOCKET" &> "$CONTAINER_OUTPUT" )

@kolyshkin
Copy link
Contributor Author

Created #3015 to investigate

@kolyshkin kolyshkin changed the title (regression?) not ok 117 update devices [minimal transition rules] (regression in master) not ok 117 update devices [minimal transition rules] Jun 9, 2021
@kolyshkin
Copy link
Contributor Author

Bad news -- I was able to reproduce this on master branch (see PR #3015), CI job https://github.com/opencontainers/runc/pull/3015/checks?check_run_id=2787947078.

Either we broke something recently, or it was always like that, I dunno.

@kolyshkin kolyshkin added this to the 1.0.0 milestone Jun 9, 2021
@kolyshkin
Copy link
Contributor Author

Adding 1.0.0 milestone just in case we did broke something recently (it's not yet clear).

@kolyshkin
Copy link
Contributor Author

@kolyshkin
Copy link
Contributor Author

Shit, I think I did a very bad thing. We need to revert #2994.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant