[CS9/master] unable to provision OC node: timeout on second boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Note: this is a new bug, discovered after https:/
Hello there,
When trying to provision the OC node using the overcloud-
It hangs on a dracut loop, as if it was waiting for a device that doesn't exist (the UUID listed in dracut log doesn't exist on the host - it was checked of course).
This UUID might be a left-over of some image build process. Since it's always the same, it's probably related to the CentOS base image itself, the one used to build the OC image:
[ 8.045500] localhost systemd[1]: Reached target Basic System.
[ 137.069543] localhost dracut-
[ 137.072352] localhost dracut-
[ 137.072352] localhost dracut-
[ 137.072352] localhost dracut-
[ 137.082038] localhost dracut-
I'll add a log file right after this LP is created.
Cheers,
C.
tags: | added: alert |
Log generated upon boot failure, its origin is /run/initramfs/ rdsosreport. txt - I could extract it from the VM.