Bug 1457747 - Can not choose flavor in dashboard if glance.min_disk > flavor.disk
Summary: Can not choose flavor in dashboard if glance.min_disk > flavor.disk
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: z4
: 10.0 (Newton)
Assignee: Beth White
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-01 08:55 UTC by Beth White
Modified: 2020-07-16 09:43 UTC (History)
16 users (show)

Fixed In Version: python-django-horizon-10.0.3-8.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1457745
Environment:
Last Closed: 2017-09-06 17:14:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
The warning message. (234.04 KB, image/png)
2017-06-02 08:16 UTC, Radomir Dopieralski
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1677206 0 None None None 2017-06-01 08:55:33 UTC
Red Hat Product Errata RHBA-2017:2658 0 normal SHIPPED_LIVE python-django-horizon bug fix advisory 2017-09-06 20:57:37 UTC

Comment 1 Red Hat Bugzilla Rules Engine 2017-06-01 08:55:50 UTC
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.

Comment 3 Radomir Dopieralski 2017-06-02 07:59:27 UTC
I tested this on python-django-horizon-10.0.3-7.el7ost

I created an image with a 2GB minimum disk, and a flavor with 0GB disk.
I can select the flavor when that disk is selected, however, there is a warning
appearing next to it, saying:

"The selected image source requires a flavor with at least 2 GB of root disk. Select a flavor with a larger root disk or use a different image source.".

I think there should be no warning when flavor's disk is 0.

Comment 4 Radomir Dopieralski 2017-06-02 08:16:06 UTC
Created attachment 1284348 [details]
The warning message.

Here's a screenshot of the dialog with the warning.

Comment 9 errata-xmlrpc 2017-09-06 17:14:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2658


Note You need to log in before you can comment on or make changes to this bug.