Bug 1109420 - [RFE] Automatically discover Image Format based on image file extension
Summary: [RFE] Automatically discover Image Format based on image file extension
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: 6.0 (Juno)
Assignee: Matthias Runge
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks: RHELOSP-RHCI
TreeView+ depends on / blocked
 
Reported: 2014-06-13 19:58 UTC by Matt Reid
Modified: 2023-02-22 23:02 UTC (History)
7 users (show)

Fixed In Version: python-django-horizon-2014.2-4.el7ost
Doc Type: Enhancement
Doc Text:
The "Format" field in the dashboard's Create Image window is now automatically populated after the user fills out the Image Source and Image File fields. Automatic population is based on the image file's extension.
Clone Of:
Environment:
Last Closed: 2015-02-09 14:55:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1324192 0 None None None Never
OpenStack gerrit 98995 0 None None None Never
Red Hat Product Errata RHEA-2015:0154 0 normal SHIPPED_LIVE python-django-horizon enhancement advisory 2015-02-09 19:52:20 UTC

Description Matt Reid 2014-06-13 19:58:35 UTC
Description of problem:
It would be great if Horizon could automatically prepopulate the "Format" field in the Create Image modal after the user has filled out the Image Source/Image File fields. This could be done based on the file extension and save the user from filling out one additional field in this modal.

Comment 2 Matthias Runge 2014-11-24 09:19:21 UTC
How to test:
============
- in images page in horizon
- push "create image" button
- select "Image file" for image source
- select source image and upload
- format should change to something other than "Select format"

Comment 5 errata-xmlrpc 2015-02-09 14:55: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://rhn.redhat.com/errata/RHEA-2015-0154.html


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