Re: [ansible-project] Re: os_volume 404 error

So, good news and good-ish news... The glance 404 problem you were experiencing should be fixed in shade. I have tested this against your cloud. We haven't released a new version with the fix yet, but you can pull in the latest code from the source repo (https://github.com/openstack-infra/shade)

Re: [ansible-project] Re: os_volume 404 error

Accounts would be most helpful and appreciated. Myself and Monty Taylor do most of the Ansible and shade development, so if we could both get access, that would go a long way to improving the modules for you. Please email me off-list to let me know what you need from us to make that happen.

Re: [ansible-project] Re: os_volume 404 error

Everything Shrews says is correct - I would love an account - and we can add a metacloud profile to os-client-config too. I'm sure you're not doing anything too crazy - it turns out that the number of ways all this can combine are large - we have all sorts of logic already to handle "normal"

Re: [ansible-project] Re: os_volume 404 error

Thanks. I'll set it up tomorrow and email you both off list. > On Sep 20, 2015, at 4:54 PM, Monty Taylor wrote: > > Everything Shrews says is correct - I would love an account - and we can add > a metacloud profile to os-client-config too. I'm sure you're not doing

[ansible-project] Re: os_volume 404 error

We aren't doing anything special on our URLs at all. Attached is the output of a keystone catalog. I would appreciate any feedback you might have on any issues you see with the catalog. As mentioned Vallard can provide access to a publicly available cloud for testing purposes. keystone

Re: [ansible-project] Re: os_volume 404 error

Ah, thanks for the info on the security group stuff. I'll try that out. I'm happy to let someone have a metacloud account to test things with. On Fri, Sep 18, 2015 at 10:23 AM, David Shrewsbury < shrewsbury.d...@gmail.com> wrote: > Sorry you're having issues. Sounds like metacloud is doing

[ansible-project] Re: os_volume 404 error

Sorry you're having issues. Sounds like metacloud is doing something we don't expect with their endpoints since you are having the same problem. This is difficult to debug without a metacloud account. Your solution to the image service problem was to add code to remove the "/v1". Does that