CI issue: Failed to get properties: Message recipient disconnected from message bus without replying
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
microovn |
Triaged
|
Undecided
|
Unassigned |
Bug Description
Our CI/tests are failing due to a bug in cloud-init [0]. It occurs if we try to run `cloud-init status --wait`[1] and dbus is not fully up yet. Fix was released in cloud-init 23.4.1 [2] but I think we need a workaround before this fixed version gets released into the package repository. Since it's a race condition, it is not 100% reproducible, but in my experience it occurs more often than not.
Reproducer:
$ make check-system
Example of error traceback:
basic_cluster.bats
✗ setup_file failed
Launching microovn-
Launching microovn-
Waiting for microovn-
Cleaning up microovn-
Cleaning up microovn-
Cleaning up microovn-
(from function `lxc_exec' in file tests/test_
from function `wait_container
from function `setup_file' in test file tests/test_
`wait_
....
File "/usr/bin/
File "/usr/lib/
retval = util.log_time(
File "/usr/lib/
ret = func(*args, **kwargs)
File "/usr/lib/
details = get_status_
File "/usr/lib/
File "/usr/lib/
stdout = subp.subp(
File "/usr/lib/
raise ProcessExecutio
cloudinit.
Command: ['systemctl', 'show', '--property=
Exit code: 1
Reason: -
Stdout:
Stderr: Failed to get properties: Message recipient disconnected from message bus without replying
[0] https:/
[1] https:/
[2]https:/
The problem seems to have gone away for now but I'll keep this open. Hopefully it wont resurface until we'll switch to 24.04 containers for the tests. 24.04 should have version of cloud-init that is not affected by this bug.