Bug 1042025 - [RFE][horizon]: Create metadata only object without a file
Summary: [RFE][horizon]: Create metadata only object without a file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Upstream M3
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact: Ido Ovadia
URL: https://blueprints.launchpad.net/hori...
Whiteboard: upstream_milestone_icehouse-3 upstrea...
Depends On:
Blocks: 1085568
TreeView+ depends on / blocked
 
Reported: 2013-12-12 20:37 UTC by RHOS Integration
Modified: 2014-09-08 05:42 UTC (History)
8 users (show)

Fixed In Version: python-django-horizon-2014.1-5.el7ost
Doc Type: Enhancement
Doc Text:
Clone Of:
: 1085568 (view as bug list)
Environment:
Last Closed: 2014-07-08 15:43:44 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:0855 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement - Dashboard 2014-07-08 19:33:24 UTC

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
Note You need to log in before you can comment on or make changes to this bug.