Hyper-V: instance disk resize issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compute-hyperv |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When resizing an instance having one ephemeral disk to a new flavor having the total ephemeral disks size set to 0, the Hyper-V driver will remove the disk without detaching it from the imported VM. For this reason, the instance will fail to start (actually, fail to realize the planned VM, in Hyper-V terms).
Trace: http://
At the same time, if the instance has multiple ephemeral disks, those will be ignored, remaining attached.
When resizing from a flavor with no ephemeral storage to a new one that does have ephemeral storage, no ephemeral disk is currently added as there is no explicit ephemeral BDM. This is inconsistent with the Libvirt driver behavior as well as Hyper-V driver behavior prior to the new BDM format addition.
The flavor ephemeral storage is not validated before attempting the migration/resize, thus ending up with error state instances in case of an invalid flavor.
If the new flavor's root disk size is smaller than the current one and the instance was booted from a volume, the resize will wrongfully be rejected.
The above mentioned behavior is caused by the following method:
https:/
summary: |
- Hyper-V: resize issues when having ephemerals + Hyper-V: instance disk resize issues |
description: | updated |
Related fix proposed to branch: master /review. openstack. org/529046
Review: https:/