object_store.create_container doesn't return usable container

Bug #1422503 reported by Brian Curtin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack SDK
Fix Released
Critical
Brian Curtin

Bug Description

Since a PUT to /containers - as done from object_store.create_container(...) - doesn't return a body, we're basically returning an empty Container object back to the caller. Since we know what name the container is supposed to have, either from an object they passed in or the string, we should set that on the Container object we're sending back to them so it can be used.

Tags: proxy
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-openstacksdk (master)

Fix proposed to branch: master
Review: https://review.openstack.org/156391

Changed in python-openstacksdk:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on python-openstacksdk (master)

Change abandoned by Brian Curtin (<email address hidden>) on branch: master
Review: https://review.openstack.org/156391
Reason: This is not the right approach - the problem is deeper and needs updates to the resource itself

Revision history for this message
Terry Howe (thowe-g) wrote :

Is this still a thing?

Revision history for this message
Brian Curtin (brian.curtin) wrote :

This was fixed somewhat recently after converting object_store's proxy away from its one-off implementation to work with BaseProxy.

Changed in python-openstacksdk:
status: In Progress → Fix Committed
importance: Undecided → Critical
milestone: none → 0.6
tags: added: proxy
Changed in python-openstacksdk:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.