When running “ibm_compute_vm_instance”, it gets the Error: \"public_bandwidth_unlimited\": conflicts with private_network_only"

[tnakajo]

I have a support case inquiring about IBM Cloud Collection for Ansible. As he runs “ibm_compute_vm_instance”, he gets the error Error: \"public_bandwidth_unlimited\": conflicts with private_network_only". Can someone help this issue?

https://github.com/IBM-Cloud/ansible-collection-ibm/blob/master/docs/ibm_compute_vm_instance.rst

Playbook:

- name: Create IBM Cloud Classic VSI
  hosts: localhost
  collections:
   - ibmcloud.ibmcollection
  tasks:
    - name: Configure Classic VSI
      ibm_compute_vm_instance:
        ibmcloud_api_key: "_GjZbkWy3anS********************"
        public_security_group_ids: [2924108]
        hostname: "test11"
        domain: "Ansible-Sales.cloud"
        os_reference_code: "CENTOS_7_64"
        cores: 1
        memory: 1024
        disks: [25]
        region: "TOK02"

Error Message:

TASK [Configure Classic VSI] 
fatal: [localhost]: FAILED! => {"changed": false, "msg": "", "rc": 1, "resource": {"_name": "ansible_20200613-091528", "_type": "ibm_compute_vm_instance", "target": "ibm_compute_vm_instance.ansible_20200613-091528"}, "stderr": "\nError: \"public_bandwidth_unlimited\": conflicts with private_network_only\n\n  on ibm_compute_vm_instance_ansible_20200613-091528.tf line 1, in resource \"ibm_compute_vm_instance\" \"ansible_20200613-091528\":\n   1: resource ibm_compute_vm_instance \"ansible_20200613-091528\" {\n\n\n", "stderr_lines": ["", "Error: \"public_bandwidth_unlimited\": conflicts with private_network_only", "", "  on ibm_compute_vm_instance_ansible_20200613-091528.tf line 1, in resource \"ibm_compute_vm_instance\" \"ansible_20200613-091528\":", "   1: resource ibm_compute_vm_instance \"ansible_20200613-091528\" {", "", ""], "stdout": "", "stdout_lines": []}

• Tested to remove public_security_group_ids: [2924108], it gets the same error.
• Tried public_bandwidth_unlimited: 'false', it gets the same error.

[tnakajo]

I noticed there is the same issue reported in https://github.com/IBM-Cloud/ansible-collection-ibm/issues/11. I'm waiting if the workaround resolves.