Cannot execute Ansible playbook to provision DigitalOcean droplets

Posted June 6, 2020 1.1k views

I am trying to execute this playbook that provisions two droplets from a CentOS 7 VM on VMWare Fusion running Ansible 2.9.9. Already have exported my API token as environment variables TOKEN and DOAPITOKEN with the correct PAT. Also registered the SSH keys of the CentOS7 VM and the host MacBook on my DigitalOcean account.

# original source:
- hosts: localhost
  connection: local
  gather_facts: false

    - name: create one droplet..
        unique_name: yes
        region: 'nyc1'
        image: 'ubuntu-18-10-x64'
        wait_timeout: 100
        name: 'plswork-do-test1' #"{{ item }}"
        size: 's-1vcpu-1gb'
        state: present
      register: created_droplets
        - "tmp-droplet-1"
        - "tmp-droplet-2"

    - name: add to dynamic inventory
        name: '{{ created_droplets.ip_address }}'
        group: pap6-test
      with_items: '{{ created_droplets.results }}'

    - debug:
        msg: 'ID is {{ }}, IP is {{ }}'

When I execute this playbook, it fails with following error.

PLAY [localhost] ****************************************************************************************

TASK [create one droplet..] *****************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "You specified an invalid image for Droplet creation."}

PLAY RECAP **********************************************************************************************
localhost                  : ok=0    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0   

Since it mentions an invalid image, I checked the slugs of the image,region and size, all of which were correct. I am able to curl to to provision droplets. What should I do in order to resolve this problem? Is this a common issue? How do you provision DigitalOcean Droplets using Ansible?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer

Hi there @nhyun,

It looks like you are using ubuntu-18-10-x64 which does not exist, can you try changing it to ubuntu-18-04-x64?

Let me know how it goes.