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.
Bug 1956774 - private_ip expected as String, not Boolean when creating a host via the API
Summary: private_ip expected as String, not Boolean when creating a host via the API
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - Azure
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.10.0
Assignee: Evgeni Golov
QA Contact: Jitendra Yejare
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 11:49 UTC by Evgeni Golov
Modified: 2021-11-16 14:11 UTC (History)
1 user (show)

Fixed In Version: tfm-rubygem-foreman_azure_rm-2.2.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:10:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 32500 0 Normal New private_ip expected as String, not Boolean when creating a host via the API 2021-05-04 11:49:46 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:11:10 UTC

Description Evgeni Golov 2021-05-04 11:49:44 UTC
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".

Comment 1 Evgeni Golov 2021-05-04 11:49:50 UTC
Created from redmine issue https://projects.theforeman.org/issues/32500

Comment 2 Evgeni Golov 2021-05-04 11:49:52 UTC
Upstream bug assigned to egolov

Comment 3 Jitendra Yejare 2021-07-01 09:34:10 UTC
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.

Comment 4 Jitendra Yejare 2021-07-01 09:39:13 UTC
Verified in Satellite 6.10 Snap 7.

Comment 7 errata-xmlrpc 2021-11-16 14:10:50 UTC
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


Note You need to log in before you can comment on or make changes to this bug.