** Changed in: nova
Status: Fix Released => New
--
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/1392527
Title:
[OSSA 2015-017] Deleting instance while resize instance is running
leads to unuseable compute nodes (CVE-2015-3280)
Status in OpenStack Compute (nova):
New
Status in OpenStack Compute (nova) juno series:
In Progress
Status in OpenStack Compute (nova) kilo series:
Fix Committed
Status in OpenStack Security Advisory:
Fix Committed
Bug description:
Steps to reproduce:
1) Create a new instance,waiting until it’s status goes to ACTIVE state
2) Call resize API
3) Delete the instance immediately after the task_state is “resize_migrated”
or vm_state is “resized”
4) Repeat 1 through 3 in a loop
I have kept attached program running for 4 hours, all instances
created are deleted (nova list returns empty list) but I noticed
instances directories with the name “<instance_uuid>_resize> are not
deleted from the instance path of the compute nodes (mainly from the
source compute nodes where the instance was running before resize). If
I keep this program running for couple of more hours (depending on the
number of compute nodes), then it completely uses the entire disk of
the compute nodes (based on the disk_allocation_ratio parameter
value). Later, nova scheduler doesn’t select these compute nodes for
launching new vms and starts reporting error "No valid hosts found".
Note: Even the periodic tasks doesn't cleanup these orphan instance
directories from the instance path.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1392527/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
