You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
azure_rm_networkinterface:
resource_group: rgName
name: nicName
virtual_network: vnetName
subnet: subnetName
ip_configurations:
- name: ipconfig1
primary: yes
### Missing a version parameter here, for which internal IP type it should dynamically create??
public_ip_address_name: public_ipv4_name
- name: ipconfig2
### Missing a version parameter here, for which internal IP type it should dynamically create??
public_ip_address_name: public_ipv6_name
OS / ENVIRONMENT
Ubuntu 20.04
STEPS TO REPRODUCE
See above
EXPECTED RESULTS
Working like it does on the portal / as it does with the arm templates, when creating it via an ARM template, you specify the address version:
That is not exposed from the azure_rm_networkinterface module.
ACTUAL RESULTS
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error creating or updating network interface nicName - Azure Error: IPVersionForPublicIpAndNicIpConfigurationMustMatch\nMessage: IP version for publicIPAddress '/subscriptions/.../resourceGroups/rgName/providers/Microsoft.Network/publicIPAddresses/public_ipv6_name', version 'IPv6' and network interface ipConfiguration '/subscriptions/.../resourceGroups/rgName/providers/Microsoft.Network/networkInterfaces/nicName/ipConfigurations/ipconfig2', version 'IPv4' must match."}
The text was updated successfully, but these errors were encountered:
SUMMARY
It's not possible to specify an IPv6 IP in the configurations.
ISSUE TYPE
COMPONENT NAME
azure_rm_networkinterface
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
Ubuntu 20.04
STEPS TO REPRODUCE
See above
EXPECTED RESULTS
Working like it does on the portal / as it does with the arm templates, when creating it via an ARM template, you specify the address version:
That is not exposed from the azure_rm_networkinterface module.
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: