| Thread Previous • Date Previous • Date Next • Thread Next |
Reviewed: https://review.openstack.org/548629
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=3233de8f0d13ad9e0223da9f1cf895aa30a6177e
Submitter: Zuul
Branch: master
commit 3233de8f0d13ad9e0223da9f1cf895aa30a6177e
Author: Beth Elwell <belwell@xxxxxxxxxx>
Date: Wed Feb 28 15:52:06 2018 +0000
Add same launch instance error handling as image to instance
Previously, when launching an instance with an instance snapshot rather
than with an image, the error handling was not as pleasant. I.e. the
volume size was not automatically set to the minimum size and the error
message would only appear after attempting to launch an instance. This
is a small patch that addresses this and makes the user experience more
friendly.
Change-Id: Ib694f66c74e90ee2e15201673de953c08cf10122
Closes-bug: #1752360
** Changed in: horizon
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1752360
Title:
Launching instance with volume created from snapshot doesn't honor
original image min_disk
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
When launching from Horizon an instance with volume creation from an
image with a min-disk parameter :
* the volume size (GB) is automatically set to the minimum size
* if I choose a volume size inferior to this minimum size I get an error message: "The Volume size must be at least xxGB).
However, when trying to launch an instance with instance snapshot, the
behaviour is much less user friendly:
* the Volume Size (GB) field is not automatically filled in with the minimum size
* the error message is not displayed before you click on the Launch Instance button
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1752360/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
