← Back to team overview

openstack team mailing list archive

nova-volumes problem after host reboot

 

Hi there,

I am dealing with this issue for a while, but could not figure out what is
going on.

After a reboot in the openstack server, I am not able to restart ANY
instance that had a nova-volume attached.
I tried the DR procedure here without any improvement:
http://docs.openstack.org/trunk/openstack-compute/admin/content/nova-disaster-recovery-process.html

The error in compute.log is:
ERROR nova.compute.manager [req-adacca25-ede8-4c6d-be92-9e8bd8578469
cb302c58bb4245cebc61e132c79c1111 768bd68a0ac149eb8e300665eb3d3950]
[instance: 3cd109e4-addf-4aa8-bf66-b69df6573cea] Cannot reboot instance:
iSCSI device not found at
/dev/disk/by-path/ip-10.100.200.120:3260-iscsi-iqn.2010-10.org.openstack:volume-20db45cc-c97f-4589-9c9f-ed283b0bc16e-lun-1

This is a very restrictive issue, because I can not simply attach volumes
to instances knowing that in a power failure or reboot for maintenance I
will have my instances unavailable.

Below there is some info about my setup.
Any idea? Anything!
:)

Linux nova-controller 2.6.32-279.11.1.el6.x86_64 #1 SMP Tue Oct 16 15:57:10
UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

rpm -qa |grep openstack
openstack-nova-api-2012.2-2.el6.noarch
openstack-dashboard-2012.2-3.el6.noarch
openstack-utils-2012.2-5.el6.noarch
openstack-nova-volume-2012.2-2.el6.noarch
openstack-nova-novncproxy-0.4-2.el6.noarch
openstack-nova-common-2012.2-2.el6.noarch
openstack-nova-console-2012.2-2.el6.noarch
openstack-nova-network-2012.2-2.el6.noarch
openstack-nova-compute-2012.2-2.el6.noarch
openstack-nova-cert-2012.2-2.el6.noarch
openstack-nova-2012.2-2.el6.noarch
openstack-glance-2012.2-2.el6.noarch
python-django-openstack-auth-1.0.2-3.el6.noarch
openstack-nova-objectstore-2012.2-2.el6.noarch
openstack-nova-scheduler-2012.2-2.el6.noarch
openstack-keystone-2012.2-1.el6.noarch


-- 
--
Ronivon C. Costa
IBM Certified for Tivoli Software
ITIL V3 Certified
Tlm: (+351) 96 676 4458
Skype: ronivon.costa
BLog ((hosted in my own personal cloud infrastructure):
http://cloud0.dyndns-web.com/blog/

Follow ups