It's also happening in Grizzly release (nova).:
root@control01:/home/user1# nova delete vm1-acc68897-1155-45c8-b8e8-37e27a9899bd
HTTPConnectionPool(host='192.168.220.40', port=8774): Max retries exceeded with
url:
/v2/e54c7f63e9284138ad207559ca4a40e4/servers/acc68897-1155-45c8-b8e8-37e27a9899bd
** Changed in: nova
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012551
Title:
Cannot delete instance in ERROR status
To manage notifications about th
I am not able to reproduce this at all on Grizzly.
** Changed in: nova (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012551
Title:
Cannot delete ins
I am not able to reproduce this at all on Grizzly.
** Changed in: nova
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012551
Title:
Cannot delete instance
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012551
Title:
Cannot delete instance in ERROR status
To manage notifications about this bug go to:
https://bugs.launchpad.n
** Changed in: nova (Ubuntu)
Status: New => Triaged
** Changed in: nova (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012551
Title:
Cannot delete
As pointed out to me by ev0ldave in #openstack the way to fix this is to
figure out exactly what the instance ID is.
$ mysql -u root -p
mysql> USE nova;
mysql> SELECT id, host, hostname FROM instances;
...
mysql> UPDATE instances SET deleted=1, deleted_at="2012-10-10 14:56:30",
vm_state="deleted"
Here's the debug info from Folsom.
$ nova --debug delete 3935bacf-63c5-4b19-9375-f067d75d56e6
REQ: curl -i http://192.168.200.135:35357/v2.0/tokens -X POST -H
"Content-Type: application/json" -H "Accept: application/json" -H "User-
Agent: python-novaclient" -d '{"auth": {"tenantName": "dev",
"pas
You can reproduce this problem very quickly on a freshly installed
Ubuntu 12.04 system with Folsom by following the user manual line for
line due to bug #1064749
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a mem
