| 2017-08-31 13:25:33 |
Lucian Petrut |
bug |
|
|
added bug |
| 2017-08-31 20:53:32 |
Matt Riedemann |
marked as duplicate |
|
1705683 |
|
| 2017-08-31 20:53:42 |
Matt Riedemann |
removed duplicate marker |
1705683 |
|
|
| 2017-08-31 20:54:06 |
Matt Riedemann |
tags |
|
compute |
|
| 2017-09-01 07:06:07 |
Lucian Petrut |
description |
When the nova-compute service cleans up an instance that still exists on the host although being deleted from the DB, the according network info is not properly retrieved.
For this reason, vif ports will not be cleaned up.
In this situation there may also be stale volume connections. Those will be leaked as well as os-brick attempts to flush those inaccessible devices, which will fail. As per a recent os-brick change, a 'force' flag must be set in order to ignore flush errors.
Log: http://paste.openstack.org/raw/620048/ |
When the nova-compute manager periodic task cleans up an instance that still exists on the host although being deleted from the DB, the according network info is not properly retrieved. For this reason, vif ports will not be cleaned up.
In this situation there may also be stale volume connections. Those will be leaked as well as os-brick attempts to flush those inaccessible devices, which will fail. As per a recent os-brick change, a 'force' flag must be set in order to ignore flush errors.
Log: http://paste.openstack.org/raw/620048/ |
|
| 2017-09-01 07:07:57 |
Lucian Petrut |
description |
When the nova-compute manager periodic task cleans up an instance that still exists on the host although being deleted from the DB, the according network info is not properly retrieved. For this reason, vif ports will not be cleaned up.
In this situation there may also be stale volume connections. Those will be leaked as well as os-brick attempts to flush those inaccessible devices, which will fail. As per a recent os-brick change, a 'force' flag must be set in order to ignore flush errors.
Log: http://paste.openstack.org/raw/620048/ |
When the '_cleanup_running_deleted_instances' nova-compute manager periodic task cleans up an instance that still exists on the host although being deleted from the DB, the according network info is not properly retrieved. For this reason, vif ports will not be cleaned up.
In this situation there may also be stale volume connections. Those will be leaked as well as os-brick attempts to flush those inaccessible devices, which will fail. As per a recent os-brick change, a 'force' flag must be set in order to ignore flush errors.
Log: http://paste.openstack.org/raw/620048/ |
|
| 2017-09-05 07:49:37 |
jichenjc |
bug |
|
|
added subscriber jichenjc |
| 2017-10-10 03:08:04 |
Xuanzhou Perry Dong |
nova: assignee |
|
Xuanzhou Perry Dong (oss-xzdong) |
|
| 2017-10-11 08:08:03 |
Xuanzhou Perry Dong |
nova: status |
New |
Invalid |
|
| 2017-10-12 02:53:22 |
Xuanzhou Perry Dong |
nova: status |
Invalid |
Incomplete |
|
| 2017-10-12 04:05:03 |
Xuanzhou Perry Dong |
attachment added |
|
cmd_log https://bugs.launchpad.net/nova/+bug/1714247/+attachment/4968246/+files/cmd_log |
|
| 2017-10-12 09:45:29 |
Lucian Petrut |
attachment added |
|
VM cleanup issues repro cmd log https://bugs.launchpad.net/nova/+bug/1714247/+attachment/4968493/+files/vm_cleanup_cmd_log |
|
| 2017-10-13 06:35:22 |
Xuanzhou Perry Dong |
nova: status |
Incomplete |
Confirmed |
|
| 2018-07-31 15:52:34 |
Matt Riedemann |
nova: assignee |
Xuanzhou Perry Dong (oss-xzdong) |
|
|
