Public bug reported:
Although nova-manage cell_v2 verify_instance is used to check if the
provided instance is correctly mapped to a cell or not, this should not
be returning a valid mapping message if the instance itself is deleted.
It should return an error message saying 'The instance does not exist'.
Steps to reproduce :
1. Create an instance :
-> nova boot --image 831bb8a0-9305-4cd7-b985-cbdadfb5d3db --flavor m1.nano test
-> nova list
+--------------------------------------+--------+--------+------------+-------------+---------------------------------+
| ID | Name | Status | Task State | Power
State | Networks |
+--------------------------------------+--------+--------+------------+-------------+---------------------------------+
| aec6eb34-6aaf-4883-8285-348d40fdac87 | test | ACTIVE | - | Running
| public=2001:db8::4, 172.24.4.9 |
+--------------------------------------+--------+--------+------------+-------------+---------------------------------+
2. Delete the instance :
-> nova delete test
Request to delete server test has been accepted.
-> nova list
+--------------------------------------+--------+--------+------------+-------------+---------------------------------+
| ID | Name | Status | Task State | Power
State | Networks |
+--------------------------------------+--------+--------+------------+-------------+---------------------------------+
+--------------------------------------+--------+--------+------------+-------------+---------------------------------+
3. Verify Instance :
-> nova-manage cell_v2 verify_instance --uuid
aec6eb34-6aaf-4883-8285-348d40fdac87
Instance aec6eb34-6aaf-4883-8285-348d40fdac87 is in cell: cell5
(c5ccba5d-1a45-4739-a5dd-d665a1b19301)
Basically the message that we get is misleading for a deleted instance.
This is because verify_instance queries the instance_mappings table
which maintains a mapping of the deleted instances as well.
** Affects: nova
Importance: Undecided
Assignee: Surya Seetharaman (tssurya)
Status: New
** Tags: cells nova-manage
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1724621
Title:
nova-manage cell_v2 verify_instance returns a valid instance mapping
even after the instance is deleted
Status in OpenStack Compute (nova):
New
Bug description:
Although nova-manage cell_v2 verify_instance is used to check if the
provided instance is correctly mapped to a cell or not, this should
not be returning a valid mapping message if the instance itself is
deleted. It should return an error message saying 'The instance does
not exist'.
Steps to reproduce :
1. Create an instance :
-> nova boot --image 831bb8a0-9305-4cd7-b985-cbdadfb5d3db --flavor m1.nano
test
-> nova list
+--------------------------------------+--------+--------+------------+-------------+---------------------------------+
| ID | Name | Status | Task State | Power
State | Networks |
+--------------------------------------+--------+--------+------------+-------------+---------------------------------+
| aec6eb34-6aaf-4883-8285-348d40fdac87 | test | ACTIVE | - |
Running | public=2001:db8::4, 172.24.4.9 |
+--------------------------------------+--------+--------+------------+-------------+---------------------------------+
2. Delete the instance :
-> nova delete test
Request to delete server test has been accepted.
-> nova list
+--------------------------------------+--------+--------+------------+-------------+---------------------------------+
| ID | Name | Status | Task State | Power
State | Networks |
+--------------------------------------+--------+--------+------------+-------------+---------------------------------+
+--------------------------------------+--------+--------+------------+-------------+---------------------------------+
3. Verify Instance :
-> nova-manage cell_v2 verify_instance --uuid
aec6eb34-6aaf-4883-8285-348d40fdac87
Instance aec6eb34-6aaf-4883-8285-348d40fdac87 is in cell: cell5
(c5ccba5d-1a45-4739-a5dd-d665a1b19301)
Basically the message that we get is misleading for a deleted
instance. This is because verify_instance queries the
instance_mappings table which maintains a mapping of the deleted
instances as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1724621/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
