How to have unique_name with Ansible and DO?

April 21, 2016 2.3k views
Ansible Configuration Management Ubuntu
carsoncole
By:
carsoncole

Trying to get my Ansible playbook to keep unique_names, but I can't get this feature to work. Followed the tutorial on Ansible with DO 2.0 Api, but every time I run my playbook, totally new droplets are created with the SAME names!

Here's my playbook, which otherwise works fine.

---
- hosts: digitalocean

  vars:
    do_token: xxxx
    droplets:
    - droplet-one
    - droplet-two

  tasks:
  - name: ensure key exists at DigitalOcean
    digital_ocean: >
      state=present
      command=ssh
      name=demo
      ssh_pub_key={{ lookup('file', '~/.ssh/id_rsa.pub') }}
      api_token={{ do_token }}
    register: demo


  - name: ensure droplets exist
    digital_ocean:
      state: present
      command: droplet
      name: "{{item}}"
      unique_name: yes
      size_id: 512mb
      region_id: sfo1
      image_id: 15764687
      private_networking: "yes"
      ssh_key_ids: "{{ demo.ssh_key.id }}"
      api_token: "{{ do_token }}"
    with_items: "{{droplets}}"
    register: droplet_details

  - debug: msg="IP is {{ item.droplet.ip_address }}"
    with_items: droplet_details.results
1 comment
  • carsoncole April 22, 2016

    Using dopy 0.3.5, the private networking option also does not work, however will work if you use dopy 0.3.6.

    dopy 0.3.7 is broken and will cause a

    NameError: name 'DoError' is not defined
Log In to Comment
2 Answers
BrookDO April 21, 2016

Hi,

One thing I noticed that would cause this is that your uniquename: yes statement should instead be uniquename=yes to match the tutorial:

  • name: ensure droplet one exists digitalocean: > state=present command=droplet name=droplet-one uniquename=yes size_id=512mb Additionally, it's likely the dual name declarations will cause an issue - It looks like you will need to use either - name: ensure key exists at DigitalOcean or - name: ensure droplets exist for this to work as expected.
Reply
  • carsoncole April 22, 2016

    Hi Brook,
    Thanks for helping.

    Either format seems to work (and frankly is easier to read using key:value), and in fact it otherwise works fine with no errors, with all of the set values, for size, region, image_id etc. Just to be sure, I converted the format back to the tutorial and it was no different: every time I ran it, another droplet is created with the same name.

        - name: Ensure droplet exists
      digital_ocean: >
        state=present
        command=droplet
        name=droplet-test
        unique_name=yes
        size_id=512mb
        region_id=sfo1
        image_id=ubuntu-14-04-x64
        private_networking=yes
        ssh_key_ids="{{ demo.ssh_key.id }}"
        api_token="{{ do_token }}"
      register: droplet_details

    As for your second point, my 'names' for the two tasks are different, so there shouldn't be any issues? Maybe I'm not understanding.

    - name: ensure key exists at DigitalOcean
- name: Ensure droplet exists

    I'm wondering if its my version of Ansible at 2.0.2.0.

ulutter March 14, 2017

I had the same issue. Downgrading ansible to version 2.0 worked for me:

sudo pip install 'ansible>=2.0,<2.1'

If you then run your playbook you will see the following deprecation warning which points to the actual issue with latest ansible versions:

[DEPRECATION WARNING]: Using bare variables is deprecated. Update your playbooks so that the environment value uses the
 full variable syntax ('{{droplet_details.results}}').
This feature will be removed in a future release. Deprecation
warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

Hope that helps somebody :)

Reply
Have another answer? Share your knowledge.

Related Questions