We may need some discussion on this. Actually, for now, nova CAN reboot a STOPPED instance.
The logic is as following(as you append):
1)
2013-10-10 15:20:16.980 WARNING nova.compute.manager [req-975a1bd2-5c69-4a59-b506-7318bf599874 admin admin] [instance: 6105f3bf-7f58-4d42-bbbb-ff7186c16c36] trying to reboot a non-running instance: (state: 4 expected: 1)
2) soft reboot failed and try hard reboot.
2013-10-10 15:22:17.524 WARNING nova.virt.libvirt.driver [req-975a1bd2-5c69-4a59-b506-7318bf599874 admin admin] [instance: 6105f3bf-7f58-4d42-bbbb-ff7186c16c36] Failed to soft reboot instance. Trying hard reboot.
3) hard reboot will first destroy the instance then re-create and power on the instance.
So it seems to be a valid case. Phil, what do you think? Thanks.
We may need some discussion on this. Actually, for now, nova CAN reboot a STOPPED instance.
The logic is as following(as you append): manager [req-975a1bd2- 5c69-4a59- b506-7318bf5998 74 admin admin] [instance: 6105f3bf- 7f58-4d42- bbbb-ff7186c16c 36] trying to reboot a non-running instance: (state: 4 expected: 1) libvirt. driver [req-975a1bd2- 5c69-4a59- b506-7318bf5998 74 admin admin] [instance: 6105f3bf- 7f58-4d42- bbbb-ff7186c16c 36] Failed to soft reboot instance. Trying hard reboot.
1)
2013-10-10 15:20:16.980 WARNING nova.compute.
2) soft reboot failed and try hard reboot.
2013-10-10 15:22:17.524 WARNING nova.virt.
3) hard reboot will first destroy the instance then re-create and power on the instance.
So it seems to be a valid case. Phil, what do you think? Thanks.