diff options
| author | Chris Evich <cevich@redhat.com> | 2021-10-26 16:30:17 -0400 |
|---|---|---|
| committer | Chris Evich <cevich@redhat.com> | 2021-10-26 16:39:14 -0400 |
| commit | d53789068a6cd2269e5f899930ae6c9327eee573 (patch) | |
| tree | 758bc96c58a4140f8d166fb4516c65448adf3e0a /test/e2e/containers_conf_test.go | |
| parent | 12439543721f0c361a09866c8bba4220ef4e414c (diff) | |
| download | podman-d53789068a6cd2269e5f899930ae6c9327eee573.tar.gz podman-d53789068a6cd2269e5f899930ae6c9327eee573.tar.bz2 podman-d53789068a6cd2269e5f899930ae6c9327eee573.zip | |
Fix systemd PID1 test
Previously this test used an ad-hoc timeout mechanism to synchronize
with output of the container ID. However, depending on runtime
conditions this may not correctly correspond with complete startup
of the systemd process. Consequently this test fails under some
conditions with an error like:
`System has not been booted with systemd as init system (PID 1). Can't
operate. Failed to connect to bus: Host is down`
Fix this by using the more appropriate `WaitContainerReady()`
against output from system startup, close to finalization. In this way,
the test status command cannot run until systemd is fully operational.
Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'test/e2e/containers_conf_test.go')
0 files changed, 0 insertions, 0 deletions