Bug 1883351 - [OSP13] Multiple instances can't boot with "Boot failed: not a bootable disk" after simple reboot
Summary: [OSP13] Multiple instances can't boot with "Boot failed: not a bootable disk"...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: melanie witt
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-28 21:07 UTC by ggrimaux
Modified: 2023-12-15 19:37 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-13 02:05:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-30892 0 None None None 2023-12-15 19:37:24 UTC

Description ggrimaux 2020-09-28 21:07:49 UTC 
Description of problem:
Customer rebooted 3 instances and all of them can't boot with the BIOS error message: "Boot failed: not a bootable disk" 

The following is the work that was done for 1 of those instance. (more info to come in private comments after)

From the storage perspective all looks good.
The volume is attached to the instance and then the instance is booted.

This instance is Linux with only 1 disk.

Multipath shows the path active and up
I dd the volume and got data.

I've compared the domain (xml) from a working instance and the non working instance and couldn't see anything wrong.

We need your help to figure out what is wrong.


Version-Release number of selected component (if applicable):
OSP13 z11
openstack-nova-compute:13.0-129

How reproducible:
100% for last 3 instances rebooted

Steps to Reproduce:
1. Reboot an instance
2.
3.

Actual results:
Instance won't boot

Expected results:
Instance boot

Additional info:
More info to come below in private comments
Note You need to log in before you can comment on or make changes to this bug.