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 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
>
>
> On Friday, September 18, 2015 at 9:51:24 AM UTC-4, vallard wrote:
>>
>> 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.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Ansible Project" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/ansible-project/FwZthkNjlWA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/b1f2f593-bf38-4979-809c-f3d3d33fa9c6%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/b1f2f593-bf38-4979-809c-f3d3d33fa9c6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Vallard
http://benincosa.com

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAA5DEzErHqXSVyQj7u3%2BkDy_SMkn6DyD-LJq%2Be3hGUbtm2kXTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to