# os\_volume 404 error **URL:** \ **Category:** Ansible Project\ **Created:** [September 18, 2015, 1:51pm UTC](https://forum.ansible.com/t/os-volume-404-error/19301 "2015-09-18T13:51:23Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![V\_Benincosa](https://avatars.discourse-cdn.com/v4/letter/v/ecc23a/32.png) [@V\_Benincosa](https://forum.ansible.com/u/V_Benincosa)\ **Post date:** [September 18, 2015, 1:51pm UTC](https://forum.ansible.com/t/os-volume-404-error/19301/1 "2015-09-18T13:51:23Z")
Having the same problem with os\_volume that I had with glance images where I get a 404 error. - Ansible 2.0 playbook: - name: ensure there is a volume for storing data. os\_volume: size: 40 display\_name: lab\_volume register: vol Error message: fatal: [localhost]: FAILED! =\> {“changed”: false, “failed”: true, “msg”: “Error fetching volume list: Not Found (HTTP 404)”} When I got an error like this with glance, I had to go in and modify some code in the shade library. I made sure I put the shade library back to what it was before so it shouldn’t be the issue here. My OpenStack (metacloud) uses v1 APIs of cinder. The other issue, somewhat related is using the security\_groups found in 2.0. Those don’t work with my openstack environment either because they require neutron. No neutron in my environment. ---
**Author:** ![David\_Shrewsbury1](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@David\_Shrewsbury1](https://forum.ansible.com/u/David_Shrewsbury1)\ **Post date:** [September 18, 2015, 5:23pm UTC](https://forum.ansible.com/t/os-volume-404-error/19301/2 "2015-09-18T17:23:23Z")
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 solution also fix the problem with the volume service? As for security groups, in your clouds.yaml (which I assume you are using?), you will need to set ‘secgroup\_source’ to ‘nova’. It defaults to using neutron. -Dave ---
**Author:** ![V\_Benincosa](https://avatars.discourse-cdn.com/v4/letter/v/ecc23a/32.png) [@V\_Benincosa](https://forum.ansible.com/u/V_Benincosa)\ **Post date:** [September 18, 2015, 9:26pm UTC](https://forum.ansible.com/t/os-volume-404-error/19301/3 "2015-09-18T21:26:35Z")
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. ---
**Author:** ![Chet\_Burgess](https://avatars.discourse-cdn.com/v4/letter/c/7993a0/32.png) [@Chet\_Burgess](https://forum.ansible.com/u/Chet_Burgess)\ **Post date:** [September 18, 2015, 11:12pm UTC](https://forum.ansible.com/t/os-volume-404-error/19301/4 "2015-09-18T23:12:13Z")
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 catalog Service: compute ---
**Author:** ![David\_Shrewsbury1](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@David\_Shrewsbury1](https://forum.ansible.com/u/David_Shrewsbury1)\ **Post date:** [September 20, 2015, 11:32pm UTC](https://forum.ansible.com/t/os-volume-404-error/19301/5 "2015-09-20T23:32:22Z")
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. -Dave ---
**Author:** ![Monty\_Taylor](https://avatars.discourse-cdn.com/v4/letter/m/7993a0/32.png) [@Monty\_Taylor](https://forum.ansible.com/u/Monty_Taylor)\ **Post date:** [September 20, 2015, 11:54pm UTC](https://forum.ansible.com/t/os-volume-404-error/19301/6 "2015-09-20T23:54:40Z")
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” behavior. I’m sure we’ll just find another nugger of normal 🙂 ---
**Author:** ![V\_Benincosa](https://avatars.discourse-cdn.com/v4/letter/v/ecc23a/32.png) [@V\_Benincosa](https://forum.ansible.com/u/V_Benincosa)\ **Post date:** [September 21, 2015, 2:56am UTC](https://forum.ansible.com/t/os-volume-404-error/19301/7 "2015-09-21T02:56:01Z")
Thanks. I’ll set it up tomorrow and email you both off list. ---
**Author:** ![David\_Shrewsbury1](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@David\_Shrewsbury1](https://forum.ansible.com/u/David_Shrewsbury1)\ **Post date:** [September 28, 2015, 5:07pm UTC](https://forum.ansible.com/t/os-volume-404-error/19301/8 "2015-09-28T17:07:55Z")
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](https://github.com/openstack-infra/shade)) and give that a test, if you like. Since the default image API version is 2, you should set image\_api\_version to 1 in your clouds.yaml file, or set the environment variable OS\_IMAGE\_API\_VERSION to 1, if you aren’t using a clouds.yaml. As for the volume 404 problem, I cannot reproduce that with the latest released version of shade, which is 0.14.0, against your cloud. Can you try upgrading shade and testing that again? -Dave