yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #53824
[Bug 1564896] Re: Boot Failed, Not a bootable disk
This bug lacks the necessary information to effectively reproduce and
fix it, therefore it has been closed. Feel free to reopen the bug by
providing the requested information and set the bug status back to "New".
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1564896
Title:
Boot Failed, Not a bootable disk
Status in OpenStack Compute (nova):
Invalid
Bug description:
This bug happen in my environment with these steps on liberty
release:
1. Create a instance by using centos 7 image. and boot it. every thing work well so far
2. Create 10G volume and attach it to this instance onto /dev/vda
Note: The volume is LVM based on loop device.
3. Format it and mount it, try to create file under it, work well.
4. Restart compute node with "systemctl restart"
5. When it is up, start all openstack services. and go to dashboard to start this instance, it say the install it running, but open the close to it, and found it fail to boot with the following log on screen:
****Boot Failed, Not a bootable disk*****
and the output from "nova show <this instance>" are as
[root@controller ~(keystone_admin)]# nova show bb5e9b52-0439-42a0-ac53-75a1ed25e7a8
+--------------------------------------+----------------------------------------------------------+
| Property | Value |
+--------------------------------------+----------------------------------------------------------+
| OS-DCF:diskConfig | AUTO |
| OS-EXT-AZ:availability_zone | Nova |
| OS-EXT-SRV-ATTR:host | compute001 |
| OS-EXT-SRV-ATTR:hypervisor_hostname | compute001 |
| OS-EXT-SRV-ATTR:instance_name | instance-00000051 |
| OS-EXT-STS:power_state | 1 |
| OS-EXT-STS:task_state | - |
| OS-EXT-STS:vm_state | active |
| OS-SRV-USG:launched_at | 2016-03-30T03:53:31.000000 |
| OS-SRV-USG:terminated_at | - |
| accessIPv4 | |
| accessIPv6 | |
| config_drive | |
| created | 2016-03-30T03:51:14Z |
| flavor | C1M1D20 (447288ec-4b9c-4a00-9001-8b68e7dc4ee0) |
| hostId | 375e5133fd870cec7008e67b2ffa1af6551267a593a6825c7a1bcf95 |
| id | bb5e9b52-0439-42a0-ac53-75a1ed25e7a8 |
| image | Attempt to boot from volume - no image supplied |
| key_name | ceshi |
| metadata | {} |
| name | ceph1 |
| os-extended-volumes:volumes_attached | [{"id": "059e67a5-6229-4a36-8d8a-545b02a9c160"}] |
| progress | 0 |
| security_groups | default |
| stacknet network | 192.168.30.127, 192.168.199.67 |
| status | ACTIVE |
| tenant_id | 8fc7a18927dc433aa4136a3be3548068 |
| updated | 2016-04-01T12:27:59Z |
| user_id | 284beeb5bc9245098246b733cb8371d7 |
+--------------------------------------+----------------------------------------------------------+
The highlight here is value of image： “Attempt to boot from volume -
no image supplied ”
and the use virsh dumpxml to show the disk is lost. only keep the
attached volume here, but it is that this is volume is not a bootable
volume.
<disk type='block' device='disk'>
<driver name='qemu' type='raw' cache='none'/>
<source dev='/dev/disk/by-path/ip-192.168.200.30:3260-iscsi-iqn.2010-10.org.openstack:volume-059e67a5-6229-4a36-8d8a-545b02a9c160-lun-0'/>
<backingStore/>
<target dev='vda' bus='virtio'/>
<serial>059e67a5-6229-4a36-8d8a-545b02a9c160</serial>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</disk>
<controller type='usb' index='0'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pci-root'>
<alias name='pci.0'/>
</controller>
<interface type='bridge'>
<mac address='fa:16:3e:33:d1:24'/>
<source bridge='qbr932ceb9b-bb'/>
<target dev='tap932ceb9b-bb'/>
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
The issue here is this cause the configuration for disk crash, and
lose the item for hard disk, the lead to the boot failure.
Append my environment info:
1. Host OS: Centos 7.2
2. Openstack: RDO release
openstack-cinder-7.0.1-1.el7.noarch
openstack-nova-novncproxy-12.0.0-3.94d6b69git.el7.noarch
openstack-utils-2014.2-1.el7.noarch
openstack-nova-compute-12.0.0-3.94d6b69git.el7.noarch
openstack-swift-proxy-2.5.0-1.el7.noarch
openstack-packstack-puppet-7.0.0-0.7.dev1661.gaf13b7e.el7.noarch
openstack-nova-common-12.0.0-3.94d6b69git.el7.noarch
openstack-neutron-ml2-7.0.0-2.el7.noarch
centos-release-openstack-liberty-1-4.el7.noarch
python-openstackclient-1.7.1-1.el7.noarch
openstack-glance-11.0.1-1.el7.noarch
openstack-neutron-common-7.0.0-2.el7.noarch
python2-django-openstack-auth-2.0.1-1.el7.noarch
openstack-swift-plugin-swift3-1.7-4.el7.noarch
openstack-selinux-0.6.41-1.el7.noarch
openstack-nova-scheduler-12.0.0-3.94d6b69git.el7.noarch
openstack-swift-account-2.5.0-1.el7.noarch
openstack-nova-cert-12.0.0-3.94d6b69git.el7.noarch
openstack-swift-container-2.5.0-1.el7.noarch
openstack-packstack-7.0.0-0.7.dev1661.gaf13b7e.el7.noarch
openstack-nova-api-12.0.0-3.94d6b69git.el7.noarch
openstack-nova-conductor-12.0.0-3.94d6b69git.el7.noarch
openstack-neutron-openvswitch-7.0.0-2.el7.noarch
openstack-dashboard-8.0.0-1.el7.noarch
openstack-keystone-8.0.1-1.el7.noarch
openstack-swift-2.5.0-1.el7.noarch
openstack-puppet-modules-7.0.0-1.el7.noarch
openstack-neutron-7.0.0-2.el7.noarch
openstack-nova-console-12.0.0-3.94d6b69git.el7.noarch
openstack-swift-object-2.5.0-1.el7.noarch
Note, Other instance without volume attached work well.
B.R
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1564896/+subscriptions
References
