Will do. I have been looking for an excuse to improve my python and figure out how ansible modules are written.
I'll file a ticket too since I'm sure someone else will be able to patch it much more quickly than I. On Mon, Dec 23, 2013 at 1:54 PM, Michael DeHaan <[email protected]>wrote: > Hmm. > > Please make sure there is a github ticket filed. Or if you would like to > work on this, that's fine too :) > > > > > > On Mon, Dec 23, 2013 at 4:50 PM, shaun <[email protected]> wrote: > >> The @ symbol is required by systemd for dynamic daemons that load a >> specific configuration file. For openvpn, you can have multiple .conf >> files for multiple openvpn daemons. The @ is required for openvpn to work >> on a systemd system. >> >> e.g. on my client I have >> systemctl start openvpn@workbench >> >> where workbench is the name of the conf file: >> /etc/openvpn/workbench.conf >> >> >> >> >> On Mon, Dec 23, 2013 at 1:47 PM, Michael DeHaan <[email protected] >> > wrote: >> >>> You shouldn't have to provide the "at" symbol here. >>> >>> >>> On Mon, Dec 23, 2013 at 3:48 PM, senorsmile <[email protected]>wrote: >>> >>>> I'm trying to control openvpn on an arch linux server. >>>> >>>> I am able to successfully start the service on the box with >>>> >>>>> systemctl start openvpn@server >>>> >>>> >>>> but when I try to do some from ansible I get: >>>> >>>>> failed: [laprouter] => {"failed": true, "item": ""} >>>>> msg: Failed to issue method call: Unit name [email protected] is not >>>>> valid. >>>>> >>>>> FATAL: all hosts have already failed -- aborting >>>> >>>> >>>> Here is the part of the yml config: >>>> >>>>> - name: Ensure openvpn service enabled >>>>> service: >>>>> name="openvpn@server" >>>>> state=started >>>> >>>> >>>> >>>> Is this an error in my configuration? >>>> >>>> -- >>>> 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 a topic in the >>> Google Groups "Ansible Project" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/ansible-project/jajY_-n6qps/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, 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. >>> >> >> -- >> 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 a topic in the > Google Groups "Ansible Project" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ansible-project/jajY_-n6qps/unsubscribe. > To unsubscribe from this group and all its topics, 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. > -- 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.
