Bug 1457747

Summary: Can not choose flavor in dashboard if glance.min_disk > flavor.disk
Product: Red Hat OpenStack Reporter: Beth White <beth.white>
Component: python-django-horizonAssignee: Beth White <beth.white>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 8.0 (Liberty)CC: aortega, apannu, athomas, beth.white, cchen, ikedajnk, iovadia, jpichon, kajinamit, kawamurayus, knakai, mrunge, opavlenk, rdopiera, samccann, srevivo
Target Milestone: z4Keywords: Reopened, Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-django-horizon-10.0.3-8.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1457745 Environment:
Last Closed: 2017-09-06 17:14:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The warning message. none

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