Setting wait: false in os_server results in auto_ip error

Bug #2049046 reported by James Denton
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ansible-collections-openstack
In Progress
Undecided
Unassigned

Bug Description

When attempting to set wait: false in openstack.cloud.server, Ansible reports the following:

TASK [Create baremetal machine] *******************************************************************************************************************************************************************
fatal: [block03.staging.sjc.ohthree.com]: FAILED! => {"changed": false, "msg": "Option 'auto_ip' requires 'wait: true'"}
fatal: [block05.staging.sjc.ohthree.com]: FAILED! => {"changed": false, "msg": "Option 'auto_ip' requires 'wait: true'"}
ok: [block02.staging.sjc.ohthree.com]
ok: [block04.staging.sjc.ohthree.com]
ok: [block01.staging.sjc.ohthree.com]

The auto_ip parameter defaults to 'true'. When setting auto_ip to false, the same error is reported.

Example task that fails:

tasks:
  - name: Create baremetal machine
    openstack.cloud.server:
      cloud: "{{ cloud_name }}"
      availability_zone: "nova"
      state: present
      name: "{{ inventory_hostname_short }}"
      image: "{{ image }}"
      key_name: "{{ key_name }}"
      timeout: 900
      flavor: "{{ flavor }}"
      nics:
        - net-id: "{{ network_mgmt }}"
          v4-fixed-ip: "{{ network_mgmt_address }}"
      auto_ip: false
      wait: false

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ansible-collections-openstack (master)
Changed in ansible-collections-openstack:
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.