Hi Ivan, That's the impression you would get from reading the error message (hence my comment behind it). In reality it's something weird going on with the quote expansion, I say this because when you remove the "instance_tags" it works as expected, also when I hardcode the instance_tags (instead of passing them as a parameter, it works too), and lastly when I pass in the instance_tags using "args: .. " it also works.
Different sets of quoting show that either the "instance_tags" do get passed in (using ansible-playbook -v), but with incorrect quoting or in the case where you get the authentication error the entire "instance_tag" block is eaten away (no longer visible using -v). Regards, Nico. On Thursday, April 2, 2015 at 8:54:24 PM UTC+2, Ivan Sichmann wrote: > > On Thu, Apr 2, 2015 at 12:17 PM, Nico K. <[email protected] <javascript:>> > wrote: > > > results in: msg: No handler was ready to authenticate. 1 handlers were > > checked. ['QuerySignatureV2AuthHandler'] Check your credentials (bit of > a > > weird error message too). > > I've played around with quoting for a while but I can't seem to work out > how > > to do this... > > This seems an authentication error, are you sure that your AWS access > and secret keys are visible to your task? Also, this bug [1] may be > related to the authentication error in the ec2 tagging, can you try > testing with a explicity ec2_tag action to see if you can tag > instances separatedly? > > [1] https://github.com/ansible/ansible/issues/9984 > > -- > Ivan Sichmann Freitas > -- 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/6d0aca6a-b708-4abc-8679-8894b8cadf95%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
