Created attachment 1212515 [details]
Azure CR Expects IP Address currently

Description of problem:


I believe this is a bug, Cloud Compute Resource Provider Azure expects IP addresses under network tab.

I think it should work without the need to provider IP addresses/Subnet as it is a cloud Provider and so is provided be the Cloud Provider.

Also, even if we plan to use virtual_network from that of Azure, there is no option to choose currently from the foreman UI.

2016-10-20 04:57:57 b14ad3cf [app] [I] Failed to save: Ip can't be blank, Ip6 can't be blank

Also we get this message in the /var/log/foreman/production.log as normal INFO, shouldn't this be WARNING or ERROR , because without which we can't proceed.


Version-Release number of selected component (if applicable):

Satellite6.3 SNAP5


How reproducible:


Steps to Reproduce:
1. When trying to create a new host with Azure Cloud Provider.
2. 
3.

Actual results:
Subnet association and providing IP address under networks tab looks mandatory currently.

Expected results:
Subnet association and providing IP address under networks tab looks mandatory currently.

Additional info: