OpenStack Compute (nova)

Can't delete a volume

Asked by Mike Parkhurst

localadmin@Server1:~$ nova list
+--------------------------------------+------------------+--------+----------+
| ID | Name | Status | Networks |
+--------------------------------------+------------------+--------+----------+
| 23d3e220-a9d1-42b9-8b82-5be784495654 | superfrobnicator | ACTIVE | |
+--------------------------------------+------------------+--------+----------+
localadmin@Server1:~$ nova volume-list
+----+-----------+--------------+------+-------------+-------------+
| ID | Status | Display Name | Size | Volume Type | Attached to |
+----+-----------+--------------+------+-------------+-------------+
| 7 | attaching | vol1 | 10 | None | |
+----+-----------+--------------+------+-------------+-------------+
localadmin@Server1:~$ nova volume-detach 23d3e220-a9d1-42b9-8b82-5be784495654 7
ERROR: The resource could not be found. (HTTP 404)

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Mike Parkhurst
Solved:
Last query:
Last reply:
Revision history for this message
Mike Parkhurst (mparkhurst) said : 		#1

Found the problem in that the bios did not have Hypervisor extensions turned on.

Revision history for this message
yong sheng gong (gongysh) said : 		#2

I don't see any clue here Hypervisor extensions bios setting is related.

Revision history for this message
Mike Parkhurst (mparkhurst) said : 		#3

nova-compute was not running due to the lack of Hypervisor support in the BIOS. I swapped out the CPU and then I was able to start and stop instances. It seems kind of silly that the software wou;d allow you to attempt to start an instance when the nova-compute service has started.

Revision history for this message
Mike Parkhurst (mparkhurst) said : 		#4

make that "hasn't started"..