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

containers: some tests always succeed #21044

Closed
montag451 opened this issue Dec 10, 2016 · 7 comments
Closed

containers: some tests always succeed #21044

montag451 opened this issue Dec 10, 2016 · 7 comments

Comments

@montag451
Copy link
Contributor

Since c37e76b machinectl shell is used to run commands inside containers instead of nsenter + su. However machinectl shell does not forward the return code of the command to the caller (see systemd/systemd#4215) so all the tests that use nixos-container run always succeed (e.g container-physical_interfaces.nix). So as long as systemd/systemd#4215 is not solved some tests may succeed when in fact they should have failed.

@montag451 montag451 changed the title containers: since #c37e76b some tests always succeed containers: some tests always succeed Dec 10, 2016
@montag451
Copy link
Contributor Author

montag451 commented Dec 10, 2016

cc @kampfschlaefer @wlhlm

@kampfschlaefer
Copy link
Contributor

So we need a test to check that the nixos-container tool works as expected?

Wouldn't it be kind of better to revert c37e76b until upstream fixes that?

@wlhlm
Copy link
Contributor

wlhlm commented Jan 5, 2017

I think switching to systemd-run --wait is the best option here. Also see systemd/systemd#4215 (comment)

@fpletz
Copy link
Member

fpletz commented Jan 5, 2017

@wlhlm Thanks a lot for the hint! If nobody else wants to take a shot at it I'll try to implement and test this in the next few days.

@Ekleog
Copy link
Member

Ekleog commented Nov 13, 2018

(triage) systemd/systemd#4215 has now been closed without (as far as I understand) the behavior of systemd being changed. Does someone know what was once a reproducer to check whether it's still an issue? I don't personally use machinectl :/

@wlhlm
Copy link
Contributor

wlhlm commented Nov 13, 2018

The pull request #18825 that first introduced this behavior has been reverted, so this issue shouldn't apply anymore and can be closed.

@montag451
Copy link
Contributor Author

As suggested by @wlhlm, I will close this issue as it is not relevant anymore

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

No branches or pull requests

5 participants