yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #02702
[Bug 1163844] Re: Resize instance from large flavor to small flavor based on Hyperv driver, instance status is error and the phsical instance get destroyed
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => havana-1
--
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/1163844
Title:
Resize instance from large flavor to small flavor based on Hyperv
driver, instance status is error and the phsical instance get
destroyed
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
Test script:
1.Use flavor2 to deploy instance.
2.When deployment success , resize it from flavor2 to flavor1.
3.Instance status display error.
Flavor1 information:
1 CPU
512M memory
0G disk
Flavor2 information:
1 CPU
2048M memory
20G disk
the root cause is, in current hyperv driver implementation, when to perform finish_migration operation, there is a check that the VHD can't be resize to a smaller size.
if new_size < curr_size:
raise vmutils.HyperVException(_("Cannot resize a VHD to a "
"smaller size"))
but at this point, the old instance get already destroyed, so the data could be lost.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1163844/+subscriptions