yahoo-eng-team team mailing list archive

[Akihiro Motoki <1762347@xxxxxxxxxxxxxxxxxx>]

As of Victoria (Feb 2021), swift returns 204 for an existing container.
This means some fix has been done in the swift side.

2021-02-28 09:20:37.237383 DEBUG swiftclient REQ: curl -i http://192.168.50.24:8080/v1/AUTH_af0ef1a85f544dc9b2a46404fe1943ab/new-a/ -X GET -H "X-Auth-Token: gAAAAABgO13m5ujS..."
2021-02-28 09:20:37.237540 DEBUG swiftclient RESP STATUS: 204 No Content

I did not change stable branches, but if you still hit this issue you
first need to consider backporting a swift fix rather than a workaround
in horizon.

Consider this situation, I mark it as Won't Fix.


** Changed in: horizon
       Status: Incomplete => Won't Fix

** Changed in: horizon
     Assignee: Crazik (crazik) => (unassigned)

-- 
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/1762347

Title:
  [ocata] Logout on duplicated swift container name

Status in OpenStack Dashboard (Horizon):
  Won't Fix

Bug description:
  "Create new container" form is validating name of the new container by
  checking access on Swift backend with each character entered.

  Lets create "new10" containter (when container with name "new" already
  exists in different project)

  Swift backend gets:

  GET /swift/v1/AUTH_xxxxx/n/  HTTP/1.1" 400 0 - python-swiftclient-3.3.0
  GET /swift/v1/AUTH_xxxxx/ne/  HTTP/1.1" 400 0 - python-swiftclient-3.3.0
  GET /swift/v1/AUTH_xxxxx/new/  HTTP/1.1" 401 0 - python-swiftclient-3.3.0

  Horizon gets 401 on this check, and does user logout.

  It shouldn't have a place...

  
  ENV:
  Ocata
  openstack-dashboard 3:11.0.4-0ubuntu1~cloud1
  python-swiftclient 1:3.3.0-0ubuntu1~cloud0

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1762347/+subscriptions