(resending also to list)
Right. So Basically the swift subuser wasn't created correctly. I created
issue #8587. Can you try creating a second subuser, see if it's created
correctly the second time?
On Wed, Jun 11, 2014 at 2:03 PM, David Curtiss dcurtiss_c...@dcurtiss.com
wrote:
Hmm Using
Success! You nailed it. Thanks, Yehuda.
I can successfully use the second subuser.
Given this success, I also tried the following:
$ rados -p .users.swift get '' tmp
$ rados -p .users.swift put hive_cache:swift tmp
$ rados -p .users.swift rm ''
$ rados -p .users.swift ls
hive_cache:swift2
Can you verify that the subuser object actually exist? Try doing:
$ rados ls -p .users.swift
(unless you have non default pools set)
Yehuda
On Tue, Jun 10, 2014 at 6:44 PM, David Curtiss
dcurtiss_c...@dcurtiss.com wrote:
No good. In fact, for some reason when I tried to load up my cluster VMs
Over the last two days, I set up ceph on a set of ubuntu 12.04 VMs (my
first time working with ceph), and it seems to be working fine (I have
HEALTH_OK, and can create a test document via the rados commandline tool),
but *I can't authenticate with the swift API*.
I followed the quickstart guides
On Wed, Jun 4, 2014 at 12:00 PM, David Curtiss
dcurtiss_c...@dcurtiss.com wrote:
Over the last two days, I set up ceph on a set of ubuntu 12.04 VMs (my first
time working with ceph), and it seems to be working fine (I have HEALTH_OK,
and can create a test document via the rados commandline
