This email looks remarkably similar to a bug report where I asked if you could share your authorized_key file (ideally sanitized) so we could take a look.
If this was yours please comment on the bug ticket. On Fri, Dec 27, 2013 at 4:54 PM, t2d <[email protected]>wrote: > Today, we updated from ansible 1.3 to 1.4.3 > > This part of the play worked until now > ``` > - name: ensure key files for ssh are present > action: authorized_key > user={{ item }} > key='files/{{ item }}.pub' > with_items: > - user1 > - user2 > ``` > but now, we get those errors > ``` > TASK: [common | ensure key files for ssh are present] > ************************* > failed: [example.org] => (item=user1) => {"failed": true, "item": "user1"} > msg: invalid key specified: files/user1.pub > failed: [example.org] => (item=user2) => {"failed": true, "item": "user2"} > msg: invalid key specified: files/user2.pub > ``` > The files are still in the same place. Does this happen on purpose and > what is the right way to do this now? > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Michael DeHaan <[email protected]> CTO, AnsibleWorks, Inc. http://www.ansibleworks.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 [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
