'nova reboot' under KVM always does a hard reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Vish Ishaya |
Bug Description
I really hesitate to report this as a bug because it is so hard to believe but a user reported it and I can reproduce it.
1. Booted a vm using oneiric-
2. Ssh to vm and
sudo apt-get install -y git
git clone git://github.
3. nova reboot
4. Ssh in again. The python-novaclient directory is intact but all the files have zero length
This happens often but not always. I had been using these vms myself without such a problem.
This was running stable-diablo on oneiric with kvm. I don't now what info would be more useful but on vm:
ubuntu@buggy:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/vda 10321208 687340 9109592 8% /
devtmpfs 1026112 4 1026108 1% /dev
none 205648 196 205452 1% /run
none 5120 0 5120 0% /run/lock
none 1028228 0 1028228 0% /run/shm
/dev/vdb 20642428 176196 19417656 1% /mnt
ubuntu@buggy:~$ mount
/dev/vda on / type ext4 (rw)
none on /proc type proc (rw,noexec,
none on /sys type sysfs (rw,noexec,
none on /sys/fs/
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/
devtmpfs on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,
none on /run type tmpfs (rw,noexec,
none on /run/lock type tmpfs (rw,noexec,
none on /run/shm type tmpfs (rw,nosuid,nodev)
/dev/vdb on /mnt type ext3 (rw)
summary: |
- Files in vm sometimes zeroed after 'nova reboot' + 'nova reboot' under KVM always does a hard reboot |
Changed in nova: | |
importance: | Undecided → High |
status: | Incomplete → Triaged |
Changed in nova: | |
milestone: | none → essex-4 |
assignee: | nobody → Vish Ishaya (vishvananda) |
Changed in nova: | |
milestone: | essex-4 → essex-rc1 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-rc1 → 2012.1 |
After too much manual retrying this I conclude with high probability that this does not happen if I do a reboot from the shell of the vm, only through the nova API. Furthermore, once I reboot from the vm shell, a subsequent reboot through nova does not zero the files. Strange. I wanted to try this on trystack but reboot from the dashboard is not working.