This is sort of a bug with ansible because the linode role is not idempotent. I think there are pull requests to fix this in ansible v2, but for the time being you will mostly likely have to work around it.
The linode_id does not set the ID at linode. It is to target that linode server if you need to remove or change it. This means there is no linode_id when first create it. So to work around this issue you need to comment out the ID on first run. Then you need to most likely need to add this to your linode task: `register: linode_server` then add a new task to - debug: var=linode_server this way you can see the ID that is created. Copy that ID into `linode_id` on for the next runs of the playbook to be idempotent. Hopefully they can fix this soon. On Tuesday, September 22, 2015 at 6:44:44 AM UTC-7, Iwada Eja wrote: > > Please im relatively new with ansiible and having an issue. > > Using the Linode Module to Create a new Linode instance. The Instance is > created but with the wrong linode_id > > - name: Create linode machine > linode: > api_key: 'My_Api_key' > name: server > plan: 1 > datacenter: 7 > distribution: 140 > password: 'Some_password' > linode_id: 12345678 > ssh_pub_key: 's......' > wait: yes > wait_timeout: 600 > state: present > > > I assume the Linode instance is supposed to have an Id of 12345678, but > that's not the Linode ID of the created instance. It's been set to an > arbitrary numeric value. > > Please how do i correct this? > -- 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/f3b6bc5a-33ba-4d2f-9ae0-83208ac1e80f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
