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
The interface gets provisioned with static IP 172.16.0.5 in the first task, then it gets updated to 172.16.0.6 in the second task.
Re-running the playbook should change it back to 5 and 6 again.
After the interface is initially created, the IP will not be updated.
This can be done via Azure portal without any issues.
Running the playbook a second time will report zero changes.
In the code, the logic is described to be supposed to compare the dicts of existing config with desired config, explicitly mentioning private_ip_address:
SUMMARY
Updating the static IP of an
ip_configuration
will not update it during task execution.ISSUE TYPE
COMPONENT NAME
azure_rm_networkinterface
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
N/A
STEPS TO REPRODUCE
EXPECTED RESULTS
The interface gets provisioned with static IP 172.16.0.5 in the first task, then it gets updated to 172.16.0.6 in the second task.
Re-running the playbook should change it back to 5 and 6 again.
ACTUAL RESULTS
After the interface is initially created, the IP will not be updated.
This can be done via Azure portal without any issues.
Running the playbook a second time will report zero changes.
Additional information
In the code, the logic is described to be supposed to compare the dicts of existing config with desired config, explicitly mentioning
private_ip_address
:azure/plugins/modules/azure_rm_networkinterface.py
Lines 781 to 798 in e4b6d2b
The problem appears to be that
construct_ip_configuration_set
does not includeprivate_ip_address
:azure/plugins/modules/azure_rm_networkinterface.py
Lines 952 to 968 in e4b6d2b
The text was updated successfully, but these errors were encountered: