Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1186380

Summary: When Uploading Image through web UI, can't select OVA format
Product: Red Hat OpenStack Reporter: Matt Reid <mreid>
Component: python-django-horizonAssignee: Matthias Runge <mrunge>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0 (Juno)CC: aortega, athomas, ddomingo, mrunge, nbarcet, yeylon
Target Milestone: gaKeywords: Triaged, ZStream
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-django-horizon-2015.1.0-7.el7ost Doc Type: Bug Fix
Doc Text:
When uploading an image through the dashboard, you can now select OVA as its format. In previous releases, OVA was not available as an option.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:19:44 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:

Description Matt Reid 2015-01-27 15:11:30 UTC 
Description of problem:
In our Atomic on OSP guide, we tell users to upload the Atomic OVA for RHEVM into OSP through the CLI, where you can specify the file format as OVA. When you try to do the same through the Horizon UI, there is no OVA option. Things seemed to work when I told OSP that it was a QCOW, but I wasn't sure if that would mess things up or not.

# glance image-create --name image_name --container-format ovf --is-public False --disk-format qcow2 --file RHEL-Atomic-Host-Cloud-7.0.0-Beta.rhevm.ova --progress

I'm looking at this guide - https://access.redhat.com/articles/rhel-atomic-install-rhos
Comment 3 Arthur Berezin 2015-02-11 11:04:13 UTC 
Merged for Kilo upstream.
Comment 7 Ido Ovadia 2015-07-05 10:02:23 UTC 
Verified
========
python-django-horizon-2015.1.0-10.el7ost.noarch
Comment 9 errata-xmlrpc 2015-08-05 13:19:44 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/RHEA-2015:1548