openstack
/
horizon
Code Issues Proposed changes

Reset flavors for other than "Boot from Image" source type. 

If a launched instance from "Boot from image" source type is not
meeting the given image RAM/disk requirements, the "Flavor" field
of Launch Instance will display the below message.

"Some flavors not meeting minimum image requirements have been
disabled."

And the flavors that are not meeting the specified requirements
will be disabled under "Flavor" field.

After this message has been shown if we try to choose a source
type other than "Boot from image", the flavors are still in
disabled mode and message also not being cleared.

To fix this issue, Set the image name to default when the source type
is changed from "Boot from image" to other source type.So that
disableFlavorsForImage() has been called on Image name change to
reset flavors.

Change-Id: I1a105eb84bd5d92ad521d9a8ae290912d48cf275
Closes-Bug: #1482507
(cherry picked from commit b1373e0438)
This commit is contained in:
Ragalahari 2015-09-09 19:08:42 +05:30 committed by Rob Cresswell
parent d8f62f5b00
commit 2c54748d0f
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
horizon/static/horizon/js/horizon.instances.js
View File

@ -174,6 +174,15 @@ horizon.addInitFunction(horizon.instances.init = function () {
$this.closest(".form-group").nextAll().hide();
/*
As part of fixing bug #1482507, Changing the image to default
image for other than "Boot from image" source type, so that
disableFlavorsForImages() is called on Image name change to reset flavors.
*/
if (base_type != "image_id") {
$("#id_image_id").val('');
$('#id_image_id').change();
}
switch(base_type) {
case "image_id":
elements_list = "#id_image_id";