[Yahoo-eng-team] [Bug 1699744] Re: no option to view activated capabilities
** Project changed: swift => horizon -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1699744 Title: no option to view activated capabilities Status in OpenStack Dashboard (Horizon): Invalid Bug description: Swift "list activated capabilities" can only be performed through CLI. There is no option to view swift capabilities in Horizon. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1699744/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1699730] Re: object metadata can not be created using dashboard
** Project changed: swift => horizon -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1699730 Title: object metadata can not be created using dashboard Status in OpenStack Dashboard (Horizon): New Bug description: While executing ”create object metadata" use case it is observed that , object metadata can not be created using dashboard. In case, a user want to create object metadata for an object using GUI then he can not perform the operation, as there is no link provided on dashboard to execute this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1699730/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1699722] Re: multiple objects can't be copied simultaneously using dashboard
** Also affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1699722 Title: multiple objects can't be copied simultaneously using dashboard Status in OpenStack Dashboard (Horizon): New Status in OpenStack Object Storage (swift): New Bug description: When objects are copied on dashboard, multiple objects can't be copied simultaneously using dashboard. In case, a user want to copy more than one object(multiple objects) of a container (all at same destination) then copy operation need to be executed multiple times. One can't copy multiple objects in one execution step. This feature can be introduced in Swift Openstack environment. Swift object copy option has been removed from the openstack dash board in Mitaka release. Multiple copy operation is also tried from CLI using curl command , and observed that it is not possible through CLI as well. Batch operation(selecting multiple object) should be implemented for coping object through dashboard. Code should be modified in horizon as well as in swift to handle multiple object copy. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1699722/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1469118] Re: Create new container always raise ERROR Container HEAD failed
This is not an error, in fact rest.status is returned with the exception. Look at the code in 695: https://github.com/openstack/python- swiftclient/blob/master/swiftclient/client.py#L695 The HTTP status (in this case a 404) is returned. To me the error message looks correct - doing a GET or HEAD on a non- existing container should raise an exception, because you assumed the container exists. What I could imagine is a method like "container_exists()" that will directly return a true or false and not raise an Exception; though this can be done in the client as well. Maybe the logging in horizon needs to be changed a bit? ** Also affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1469118 Title: Create new container always raise ERROR Container HEAD failed Status in OpenStack Dashboard (Horizon): New Status in Python client library for Swift: New Bug description: Following error messages raised in Horizon log file: dashboard-swiftclient: ERROR Container HEAD failed Steps: 1. Login to Horizon as admin. 2. Go to Object Store. 3. Create three containers: Container1, Container2, Container3 4. Containers created and became operable, but dashboard log contains batch of identical errors for them. It's happening because we check of exists container name https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/swift.py#L126 and swift always generate error in https://github.com/openstack/python-swiftclient/blob/master/swiftclient/client.py#L692 We need a better mechanism in swift (maybe return resp.status or something like this) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1469118/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1455102] Re: some test jobs broken by tox 2.0 not passing env variables
** Also affects: swift Importance: Undecided Status: New ** Changed in: swift Status: New => In Progress ** Changed in: swift Assignee: (unassigned) => Christian Schwede (cschwede) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1455102 Title: some test jobs broken by tox 2.0 not passing env variables Status in OpenStack Magnum: Fix Committed Status in OpenStack Neutron (virtual network service): Fix Committed Status in OpenStack Gate Infrastructure: Confirmed Status in Python client library for Cinder: Fix Committed Status in Python client library for Glance: Fix Committed Status in python-manilaclient: Fix Committed Status in Python client library for Neutron: In Progress Status in Python client library for Nova: In Progress Status in OpenStack Object Storage (Swift): In Progress Bug description: Tox 2.0 brings environment isolation, which is good. Except a lot of test jobs assume passing critical variables via environment (like credentials). There are multiple ways to fix this: 1. stop using environment to pass things, instead use a config file of some sort 2. allow explicit pass through via - http://tox.readthedocs.org/en/latest/config.html#confval-passenv =SPACE-SEPARATED-GLOBNAMES This bug mostly exists for tracking patches, and ensuring that people realize there is a larger change here. To manage notifications about this bug go to: https://bugs.launchpad.net/magnum/+bug/1455102/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1194688] Re: Devstack uses keystone.middleware.s3_token in swift pipeline
I think we can close this bug for all projects. s3_token is included in python-keystoneclient for a while now, and the s3 middleware itself is available on stackforge: https://github.com/stackforge/swift3 -> Closing bug. ** Changed in: swift Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1194688 Title: Devstack uses keystone.middleware.s3_token in swift pipeline Status in devstack - openstack dev environments: Confirmed Status in OpenStack Identity (Keystone): Invalid Status in OpenStack Object Storage (Swift): Fix Released Bug description: Coming from https://bugs.launchpad.net/keystone/+bug/1193112 devstack will use keystone's keystone.middleware.s3token when setting up swift. If it is being used externally then it shouldn't be in keystone.middleware and there are two main options for moving it: 1. s3token middleware should be moved into python-keystoneclient. This makes it available to other components in the same way that the auth_token middleware was moved. 2. s3token middleware should be moved into swift. There is already a dependency on swift.common.utils in the s3token middleware and it appears that is calling keystone via http so it should be fine to be moved. Note: this is the first time i've paid much attention to this middleware so please tell me if it needs to be a keystone thing. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1194688/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
