That's probably because no hosts are in the group when you run the config playbook.
You would need to apply those roles to a group that includes hosts. On Mon, Apr 14, 2014 at 8:48 AM, Christian Kaps <[email protected]>wrote: > Hi Michael, > > now I have additionally split up the playbooks. But now if I try to > execute only the configuration playbook, Ansible quits with the message: > "no hosts matched". In the provision playbook the hosts are added to the > mongodb host group. But it seems that these group gets not persisted. Or do > I miss something? > > Thanks, > Christian > > Am Mittwoch, 9. April 2014 16:09:04 UTC+2 schrieb Michael DeHaan: >> >> You should split your provisioning and configuration playbooks up, so >> that the provisioning playbook includes the configuration one. >> >> >> >> >> >> >> On Wed, Apr 9, 2014 at 9:33 AM, Christian Kaps <[email protected]>wrote: >> >>> Thanks, works like a charm. >>> >>> Am Dienstag, 8. April 2014 20:07:18 UTC+2 schrieb John: >>>> >>>> Hi Christian, >>>> >>>> You are correct that there is a wait parameter to the ec2 module but >>>> unfortunately it will probably not get you what you want since an ec2 >>>> instance in the "running" state does not necessary mean you can ssh to >>>> it. >>>> What we should probably add to this module is a wait for the system >>>> status check to be 'ok' which is what I do typically when using boto >>>> in python code. >>>> >>>> To solve your immediate problem I wouldn't use a prompt; instead you >>>> can wait for ssh to become available using the the wait_for module. >>>> >>>> Example: >>>> >>>> # register the var "ec2" when you launch it using the ec2 module >>>> >>>> - name: Add new instance to host group >>>> local_action: > >>>> add_host >>>> hostname={{ item.public_ip }} >>>> groupname=launched >>>> with_items: ec2.instances >>>> >>>> - name: Wait for SSH to come up >>>> local_action: > >>>> wait_for >>>> host={{ item.public_dns_name }} >>>> state=started >>>> port=22 >>>> delay=60 >>>> timeout=320 >>>> with_items: ec2.instances >>>> >>>> >>>> As for idempotent behavior with the ec2 module you can use the id >>>> parameter, see http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Run_ >>>> Instance_Idempotency.html >>>> >>>> -John >>>> >>>> >>>> On Tue, Apr 8, 2014 at 1:46 PM, Christian Kaps <[email protected]> >>>> wrote: >>>> > I think the wait property on the EC2 module is exactly what I want. >>>> > >>>> > Thanks >>>> > >>>> > Am Dienstag, 8. April 2014 09:13:59 UTC+2 schrieb Christian Kaps: >>>> >> >>>> >> Hi, >>>> >> >>>> >> in the most Playbooks about EC2 provisioning there exists a task >>>> which >>>> >> executes the pause module to wait for the instance to be available. >>>> Now that >>>> >> the EC2 module supports idempotency it is possible to run a playbook >>>> >> multiple times to add new features to an already provisioned >>>> instance. The >>>> >> problem now is that the pause module runs every time and waits for >>>> e.g. 2 >>>> >> minutes. I know that I can use ^C-c to continue the task. But I >>>> think the >>>> >> best solution would be to execute the wait task only after the >>>> instance was >>>> >> provisioned. Is there any possibility to achieve such a behavior? >>>> >> >>>> >> Cheers, >>>> >> Christian >>>> > >>>> > -- >>>> > 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/ccd1cf5f- >>>> d344-4c9f-9860-28c012bdabfc%40googlegroups.com. >>>> > >>>> > For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> 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/d96b77c1-526a-49c0-9a2c- >>> f57842c1d3ca%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/d96b77c1-526a-49c0-9a2c-f57842c1d3ca%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > 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/29b7b1e0-5b8a-4036-b699-20dce665b0ae%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/29b7b1e0-5b8a-4036-b699-20dce665b0ae%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2BnsWgyr4g%2Bk_XHTk%2B_GY4ZTXJ-aesp4uVXm5ojsSMUu5TrFqg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
