Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
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: