openstack team mailing list archive

[Marcelo Martins <btorch-os@xxxxxxxxxxxxxx>]

Hi Leandro,


If you search all swift services logs for the transaction Id returned what do you see ? 






Marcelo Martins
Openstack-swift
btorch-os@xxxxxxxxxxxxxx

“Knowledge is the wings on which our aspirations take flight and soar. When it comes to surfing and life if you know what to do you can do it. If you desire anything become educated about it and succeed. “




On Nov 23, 2011, at 8:25 AM, Leandro Reox wrote:

> Im getting 404 with both tools, curl and swift , we're using the repo where you commited 41 minutes ago 
> 
> 
> Regards
> 
> On Wed, Nov 23, 2011 at 10:51 AM, Chmouel Boudjnah <chmouel@xxxxxxxxxxxxx> wrote:
> Hi,
> 
> Which version did you use for keystone2 from cloudbuilders github
> trunk? can you try again (I just updated some fixes to it just now).
> 
> And what do you mean you are getting 404,  how do you test it ? with
> swift cli or via curl ?
> 
> Chmouel.
> 
> On Wed, Nov 23, 2011 at 2:27 PM, Leandro Reox <leandro.reox@xxxxxxxxx> wrote:
> > Hi Hugo,
> >
> > We changed out everything to keystone2 , now we're getting a 404 when we try
> > to create the container, maybe the account autocreation is not working
> > properly any thoughts ?
> >
> > Regards
> >
> > On Wed, Nov 23, 2011 at 10:20 AM, Kuo Hugo <tonytkdk@xxxxxxxxx> wrote:
> >>
> >> Hi Leandro ,
> >> Post on launchpad QA will be a better place though. Plz post it on
> >> launchpad , and we will jump to there for further discussion.
> >> 1. Verify that your keystone is running , via curl -v -H "X-Auth-User:
> >> MAX" -H "X-Auth-Key: Infa" http://%keystone_IP%:5000/v1.0
> >> If keystone working properly , should return X-Auth-Token & X-Storage-url
> >>   etc.....
> >> After  step 1 ...
> >> Use the returned X-Auth-Token and X-Storage-Url for the following cURL cmd
> >> curl -k -v -H "X-Auth-Token: %token%" %Returned
> >> X-storage-Url%  http://%Swift-proxy_IP%:8080/v1/AUTH_%tenant_id%
> >> I guess it will be
> >> curl -v -k -H "X-Auth-Token: 1234567890"
> >>   http://172.16.0.88:8080/v1/AUTH_%tenant_ID%
> >>
> >> If so , I believe that your problem is on the protocol of Swift-proxy , as
> >> your post , it's under https in your proxy-server.conf .
> >> To disable it by comment
> >> cert_file = /etc/swift/cert.crt
> >> key_file = /etc/swift/cert.key
> >> or correct the endpoint of swift to https......
> >> If you were deploying keystone via cloudbuilder/devstack script ... You
> >> might need to check the sampledata .   With swift client v1.0 , it needs the
> >> value of Tenant_Id in USERS table.
> >> Hope it help ...
> >> --
> >> +Hugo Kuo+
> >> tonytkdk@xxxxxxxxx
> >> hugo.kuo@xxxxxxxxxxxx
> >> +886-935-004-793
> >> www.cloudena.com
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack
> > Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
> >
> >
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp