delete shelve offloaded instance should delete attached port

Bug #1298381 reported by Alex Xu
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned

Bug Description

After deleted shelve offloaded instance, the port attached to instance isn't deleted.

Reproduce as below:

soulxu1304@soulxu1304-ThinkPad-T410:/opt/stack/nova$ nova shelve vm1
soulxu1304@soulxu1304-ThinkPad-T410:/opt/stack/nova$ nova shelve-offload vm1
soulxu1304@soulxu1304-ThinkPad-T410:/opt/stack/nova$ nova list
+--------------------------------------+------+-------------------+------------+-------------+--------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+------+-------------------+------------+-------------+--------------------+
| 8adb3755-b874-4ae9-a361-4924e4ed0ebc | vm1 | SHELVED_OFFLOADED | - | Shutdown | public=172.24.4.15 |
+--------------------------------------+------+-------------------+------------+-------------+--------------------+
soulxu1304@soulxu1304-ThinkPad-T410:/opt/stack/nova$ nova delete vm1
soulxu1304@soulxu1304-ThinkPad-T410:/opt/stack/nova$ neutron port-list
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| id | name | mac_address | fixed_ips |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| 1e6bed8d-aece-4d3e-abcc-3ad7957d6d72 | | fa:16:3e:9e:dc:83 | {"subnet_id": "e5dbc790-c26f-45b7-b2c7-574f12ad8b41", "ip_address": "172.24.4.12"} |
| 5f522a9a-2856-4a95-8bd8-c354c00abf0f | | fa:16:3e:01:47:43 | {"subnet_id": "94575a05-796f-4ff5-b892-3c3b8231b303", "ip_address": "10.0.0.1"} |
| 6226f6d3-3814-469c-bf50-8c99dfec481e | | fa:16:3e:46:0e:35 | {"subnet_id": "94575a05-796f-4ff5-b892-3c3b8231b303", "ip_address": "10.0.0.2"} |
| c10390a9-6f84-44f5-8a17-91cb330a9e12 | | fa:16:3e:41:7c:34 | {"subnet_id": "e5dbc790-c26f-45b7-b2c7-574f12ad8b41", "ip_address": "172.24.4.15"} |
| c814425c-be1a-4c06-a54b-1788c7c6fb31 | | fa:16:3e:f5:fc:d3 | {"subnet_id": "e5dbc790-c26f-45b7-b2c7-574f12ad8b41", "ip_address": "172.24.4.2"} |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
soulxu1304@soulxu1304-ThinkPad-T410:/opt/stack/nova$ nova list
+----+------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power State | Networks |
+----+------+--------+------------+-------------+----------+
+----+------+--------+------------+-------------+----------+

Alex Xu (xuhj)
Changed in nova:
assignee: nobody → Alex Xu (xuhj)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/83375

Changed in nova:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by Alex Xu (<email address hidden>) on branch: master
Review: https://review.openstack.org/83375

Sean Dague (sdague)
Changed in nova:
assignee: Alex Xu (xuhj) → nobody
status: In Progress → Confirmed
importance: Undecided → Medium
Revision history for this message
Radek Skokan (radek-7) wrote :

Just curious: I see a patch was submitted a year ago - any rough estimations in which release this could be fixed?
Thanks!

Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY

Changed in nova:
importance: Medium → Undecided
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.