Bug 1042025

Summary: [RFE][horizon]: Create metadata only object without a file
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: python-django-horizonAssignee: RHOS Maint <rhos-maint>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: aberezin, aortega, dnavale, iovadia, jpichon, markmc, mrunge, yeylon
Target Milestone: Upstream M3Keywords: FutureFeature, Triaged
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/horizon/+spec/metadata-only-object
Whiteboard: upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved
Fixed In Version: python-django-horizon-2014.1-5.el7ost Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1085568 (view as bug list) Environment:
Last Closed: 2014-07-08 15:43:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1085568    

Description RHOS Integration 2013-12-12 20:37:45 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/metadata-only-object.

Description:

Goal: Can create a new object in container without a file available. but I can upload the file later when it is ready. This works like a place-holder for a new object to allow user to flexibly share object metadata and URL info in advance.

A possible solution:
Use a zero byte (empty) file instead to upload at first.  In the dashboard GUI, user is not required to select a file to create an object.  There's no need to make any change for swift.

Specification URL (additional information):

None
Comment 3 Ido Ovadia 2014-06-17 14:58:21 UTC 
Verified
========
python-django-horizon-2014.1-7.el7ost.noarch
Comment 5 errata-xmlrpc 2014-07-08 15:43: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.

http://rhn.redhat.com/errata/RHEA-2014-0855.html