Bug 1012298 - swift: cli not clear for create container
Summary: swift: cli not clear for create container
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-swift
Version: 4.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Pete Zaitcev
QA Contact: Haim
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-26 08:47 UTC by Dafna Ron
Modified: 2016-04-26 17:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-18 08:06:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1231321 0 None None None Never
OpenStack gerrit 51706 0 None None None Never

Description Dafna Ron 2013-09-26 08:47:20 UTC
Description of problem:

on horizon there it's very clear but looking at the cli, since there is no create command I was unable to figure it out until I asked people who have been working with swift for a while.

If you look at the help files than post will show this:
post Updates meta information for the account, container,
                         or object

There is no indication that you can create a new empty container using this command, only change existing ones - so unless I asked i would have never guessed to use it.

Version-Release number of selected component (if applicable):

openstack-swift-1.8.0-6.el6ost.noarch

How reproducible:

100%

Steps to Reproduce:
1. run swift --help 
2. 
3.

Actual results:

its unclear how we can create a new container from cli

Expected results:

there should be a create command from containers or the help files should be clearer 

Additional info:

Comment 1 Dafna Ron 2013-09-26 08:47:57 UTC
https://bugs.launchpad.net/swift/+bug/1231321

Comment 2 Pete Zaitcev 2013-10-15 14:18:26 UTC
Fixed upstream. Dafna, would that be ok to close with resolution "upstream"?


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