udevadm settle failure on Azure Hirsute
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Low
|
Unassigned |
Bug Description
When launching a daily hirsute image, more often than not, we see a failure and traceback in the cloud-init logs:
2021-09-14 16:42:40,580 - cc_disk_
2021-09-14 16:42:40,580 - cc_disk_
2021-09-14 16:42:40,580 - cc_disk_
2021-09-14 16:42:40,581 - subp.py[DEBUG]: Running command ['udevadm', 'settle'] with allowed return codes [0] (shell=False, capture=True)
2021-09-14 16:44:40,593 - util.py[DEBUG]: Creating fs for /dev/disk/
2021-09-14 16:44:40,593 - util.py[WARNING]: Failed during filesystem operation
Unexpected error while running command.
Command: ['udevadm', 'settle']
Exit code: 1
Reason: -
Stdout:
Stderr:
2021-09-14 16:44:40,593 - util.py[DEBUG]: Failed during filesystem operation
Unexpected error while running command.
Command: ['udevadm', 'settle']
Exit code: 1
Reason: -
Stdout:
Stderr:
Traceback (most recent call last):
File "/usr/lib/
util.
File "/usr/lib/
ret = func(*args, **kwargs)
File "/usr/lib/
assert_
File "/usr/lib/
util.
File "/usr/lib/
return subp.subp(
File "/usr/lib/
raise ProcessExecutio
cloudinit.
Command: ['udevadm', 'settle']
Exit code: 1
Reason: -
Stdout:
Stderr:
2021-09-14 16:44:40,636 - handlers.py[DEBUG]: finish: init-network/
We should investigate the root cause.
Changed in cloud-init: | |
importance: | Undecided → Low |
status: | New → Triaged |
Tracked in Github Issues as https:/ /github. com/canonical/ cloud-init/ issues/ 3904