xenapi: resize down incompatible with auto_disk_config == 0
Bug #1081225 reported by
Andrew Laski
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Andrew Laski |
Bug Description
On a deployment utilizing xenapi it seems that resizing an instance down should not be an option when auto_disk_config is 0. Currently when this happens the resize up codepath is used and the instance memory is sized down, but the disk space is not. So a user could boot up an instance with the largest disk available then resize down to a smaller instance and still have the large disk on their instance. But resizing the disk down would be dangerous if the filesystem on the instance hasn't been resized first.
Changed in nova: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-2 → 2013.1 |
tags: | added: xenserver |
To post a comment you must log in.
I don't know if this actually warrants a security bug, but since there's potential for abuse in current deployments I figured I would start like this.