Bug 1387255

Summary: When using Cloud Compute Resource Azure expects population of IP addresses under networks tab while creating a New Host
Product: Red Hat Satellite Reporter: Kedar Bidarkar <kbidarka>
Component: Compute Resources - AzureAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.3.0CC: bbuckingham, bkearney, kbidarka, ktordeur
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-31 12:44:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Azure CR Expects IP Address currently none

Description Kedar Bidarkar 2016-10-20 13:12:34 UTC
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:

Comment 2 Kedar Bidarkar 2016-10-20 13:45:39 UTC
Raised an upstream issue here, http://projects.theforeman.org/issues/17046

Comment 5 Bryan Kearney 2017-08-31 12:44:21 UTC
Closing this out until we deliver https://bugzilla.redhat.com/show_bug.cgi?id=1201146.