Rebooting instance doesn't restore mounted volume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Masanori Itoh |
Bug Description
Tested on Revision No 925.
Steps to reproduce:-
1) Run one VM instance
2) Attach volume to the VM instance
3) SSH to the VM instance, mount the volume and logout from SSH
4) reboot the VM instance
5) Again SSH to the VM instance and try to mount the volume.
It doesn't allow and gives the error message
{{{
Could not stat /dev/vdb --- No such file or directory
The device apparently does not exist; did you specify it correctly?
}}}
6) euca-describe-
{{{
root@ubuntu-
VOLUME vol-00000001 1 nova in-use (admin, ubuntu-
}}}
7) If I try to detach the volume, then it gives error message in the nova-compute.log
nova-compute.log
-------
{{{
2011-04-01 17:59:04,743 ERROR nova [-] Exception during message handling
(nova): TRACE: Traceback (most recent call last):
(nova): TRACE: File "/home/
(nova): TRACE: rval = node_func(
(nova): TRACE: File "/home/
(nova): TRACE: return f(*args, **kw)
(nova): TRACE: File "/home/
(nova): TRACE: function(self, context, instance_id, *args, **kwargs)
(nova): TRACE: File "/home/
(nova): TRACE: volume_
(nova): TRACE: File "/home/
(nova): TRACE: return f(*args, **kw)
(nova): TRACE: File "/home/
(nova): TRACE: raise exception.
(nova): TRACE: NotFound: No disk at vdb
(nova): TRACE:
}}}
Related branches
- Vish Ishaya (community): Approve
- termie (community): Approve
-
Diff: 20 lines (+8/-1)1 file modifiednova/virt/libvirt_conn.py (+8/-1)
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → diablo-1 |
Changed in nova: | |
milestone: | diablo-1 → 2011.3 |
status: | Fix Committed → Fix Released |
Hi Tushar,
You use KVM on Ubuntu, right? instances.
Also, you rebooted the instance on the guest OS?
I mean, not using euca-reboot-
I'm feeling that the root cause of this issue would be a KVM problem.
If this issue is reproducible, please check collect information before and after rebooting instances on compute node.
# virsh dumpxml VM_NAME
I guess the device you attached to your VM vanished from VM configuration after guest OS reboot.
In the case, what we can do anyway would be logging the exeption and cleaning up database, I think.
-Masanori