Bug 816206 - object-storage: new account fails to update the key
Summary: object-storage: new account fails to update the key
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: GlusterFS
Classification: Community
Component: object-storage
Version: pre-release
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: ---
Assignee: Junaid
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-25 13:45 UTC by Saurabh
Modified: 2016-01-19 06:09 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-04-27 09:46:27 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Saurabh 2012-04-25 13:45:32 UTC 
Description of problem:

the new account addition fails to update the key and the REST APIs return with "403 Forbidden" error

seen with latest rpms and with original swift things work
Version-Release number of selected component (if applicable):
3.3.0qa37 and gluster-swift-1.0

How reproducible:


Steps to Reproduce:
1. add a new account in proxy-server
2. try sending GET command to server
3.
  
Actual results:
fails with 403 forbidden


Expected results:
should work without throwing the above mentioned error

Additional info:
Comment 1 Junaid 2012-04-27 09:46:27 UTC 
Saurabh,

I tried to reproduce the bug with the rpms at are due to be released with beta, the issue is not happening on them. Can you try it out on a different machine or restarting the memcached and swift servers.

For now moving to works for me. Reopen the bug if you find the issue once again.
Comment 2 Saurabh 2012-04-27 10:31:22 UTC 
I tried the same stuff on a different setup altogether and it works, hence not pursuing this presently for further investigation.
Note You need to log in before you can comment on or make changes to this bug.