I’ve got a bit more verbosity:
<10.220.226.90> REMOTE_MODULE lvg vg=vg.osddata.raven state=present
pvs=/dev/xvdb,/dev/xvdc
looks like the module is getting the correct data?
On Tuesday, January 20, 2015 at 1:53:31 PM UTC+1, Mark Maas wrote:
Tried it with this:
>
> - name: Maak een vg-tc
> lvg:
> vg: vg.osddata.raven
> pvs: /dev/xvdb,/dev/xvdc
> state: present
>
> But still no go:
>
> failed: [10.220.226.90] => {"err": " Device /dev/xvdb /dev/xvdc not found
> (or ignored by filtering).\n Unable to add physical volume '/dev/xvdb
> /dev/xvdc' to volume group 'vg.osddata.raven'.\n", "failed": true, "rc": 5}
> msg: Creating volume group 'vg.osddata.raven' failed
>
> Thanks for looking btw!
>
> On Tuesday, January 20, 2015 at 1:36:26 PM UTC+1, Brian Coca wrote:
>
> there is current bug in = option parser, try this:
>> 1
>> - name: Maak een vg-tc
>> lvg:
>> vg: vg.osddata.raven
>> pvs: /dev/xvdb,/dev/xvdc
>> state: present
>>
>> --
>> Brian Coca
>>
>
>
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/66b35d93-e8fa-4049-8097-65629765714a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
