Error 422: Public ipv4 subnet size '31' is invalid for VMware ESXi 7.0

[jpablo-eqx]

SUMMARY

It seems equinix.metal.device is deploying with a default /31 subnet even on ESXI and Windows. Deploying fails with the error:

ESXI:

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: packet.baseapi.ResponseError: Error 422: Public ipv4 subnet size '31' is invalid for VMware ESXi 7.0
fatal: [localhost]: FAILED! => {"changed": false, "msg": "failed to set device state present, error: Error 422: Public ipv4 subnet size '31' is invalid for VMware ESXi 7.0"}

Windows:

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: packet.baseapi.ResponseError: Error 422: Public ipv4 subnet size '31' is invalid for Windows 2019 Standard
fatal: [localhost]: FAILED! => {"changed": false, "msg": "failed to set device state present, error: Error 422: Public i
pv4 subnet size '31' is invalid for Windows 2019 Standard"}

ISSUE TYPE

• Bug Report

COMPONENT NAME

equinix.metal.device

ANSIBLE VERSION

ansible [core 2.12.2]
  config file = None
  configured module search path = ['/Users/user/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /Users/user/projects/equinix-metal/ansible/windowstest/.venv/lib/python3.9/site-packages/ansible
  ansible collection location = /Users/user/.ansible/collections:/usr/share/ansible/collections
  executable location = /Users/user/projects/equinix-metal/ansible/windowstest/.venv/bin/ansible
  python version = 3.9.10 (main, Jan 15 2022, 11:48:00) [Clang 13.0.0 (clang-1300.0.29.3)]
  jinja version = 3.0.3
  libyaml = True

CONFIGURATION

none

OS / ENVIRONMENT

Mac OS

STEPS TO REPRODUCE

  tasks:
    - name: deploy esxi
      equinix.metal.device:
        count: 1
        hostnames: jp-ansible-module-01
        operating_system: vmware_esxi_7_0
        plan: c3.small.x86
        facility: sv15
        project_id: "{{ project_id }}"
        api_token: "{{ api_token }}"

EXPECTED RESULTS

Will deploy esxi with /29 private/public IP which is the default behaviour of the API

ACTUAL RESULTS

Deploying Windows / ESXI fails with the error:

ESXI:

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: packet.baseapi.ResponseError: Error 422: Public ipv4 subnet size '31' is invalid for VMware ESXi 7.0
fatal: [localhost]: FAILED! => {"changed": false, "msg": "failed to set device state present, error: Error 422: Public ipv4 subnet size '31' is invalid for VMware ESXi 7.0"}

Windows:

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: packet.baseapi.ResponseError: Error 422: Public ipv4 subnet size '31' is invalid for Windows 2019 Standard
fatal: [localhost]: FAILED! => {"changed": false, "msg": "failed to set device state present, error: Error 422: Public i
pv4 subnet size '31' is invalid for Windows 2019 Standard"}