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.
I am creating Azure VMs using the API (well, Ansible, but that doesn't matter).
I submit the following Interfaces config:
<pre>
interfaces_attributes:
- type: "interface"
compute_attributes:
network: default #not foreman-vnet-default
public_ip: Dynamic
private_ip: false
</pre>
Which yields the following error:
<pre>
MsRestAzure::AzureOperationError: PrivateIPAddressMissing: Private IP address is required when privateIPAllocationMethod is Static in IP configuration /subscriptions/UUID/resourceGroups/foreman/providers/Microsoft.Network/networkInterfaces/whoa-nic0/ipConfigurations/whoa-nic0.
</pre>
This is because the code at https://github.com/theforeman/foreman_azure_rm/blob/48c22cb6f4e3845d2faf61be26d3f0eea58b6b70/app/models/concerns/foreman_azure_rm/vm_extensions/managed_vm.rb#L126 reads:
<pre>
private_ip = (attrs[:private_ip] == 'false') ? false : true
</pre>
Which makes private_ip only False if the API parameter was a *string* with the value "false".
Verified!
Steps:
1. Create an Azure RM Compute Resource.
2. Provision the host on Azure CR but by setting private_ip to False(Boolean, not String) in interface attributes of host.
Behaviour:
The host provisioned is successful even though the private_ip is set to boolean value.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2021:4702
I am creating Azure VMs using the API (well, Ansible, but that doesn't matter). I submit the following Interfaces config: <pre> interfaces_attributes: - type: "interface" compute_attributes: network: default #not foreman-vnet-default public_ip: Dynamic private_ip: false </pre> Which yields the following error: <pre> MsRestAzure::AzureOperationError: PrivateIPAddressMissing: Private IP address is required when privateIPAllocationMethod is Static in IP configuration /subscriptions/UUID/resourceGroups/foreman/providers/Microsoft.Network/networkInterfaces/whoa-nic0/ipConfigurations/whoa-nic0. </pre> This is because the code at https://github.com/theforeman/foreman_azure_rm/blob/48c22cb6f4e3845d2faf61be26d3f0eea58b6b70/app/models/concerns/foreman_azure_rm/vm_extensions/managed_vm.rb#L126 reads: <pre> private_ip = (attrs[:private_ip] == 'false') ? false : true </pre> Which makes private_ip only False if the API parameter was a *string* with the value "false".