Bug 1497202 - When provisioning an Azure instance and selecting NONE for the Public IP Address option a public IP is still assigned.
Summary: When provisioning an Azure instance and selecting NONE for the Public IP Addr...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.8.0
Hardware: All
OS: All
unspecified
high
Target Milestone: GA
: 5.10.0
Assignee: Daniel Berger
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks: 1530728 1531256
TreeView+ depends on / blocked
 
Reported: 2017-09-29 13:06 UTC by Ryan Spagnola
Modified: 2021-03-11 15:53 UTC (History)
11 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1530728 1531256 (view as bug list)
Environment:
Last Closed: 2018-06-21 20:43:29 UTC
Category: Feature
Cloudforms Team: Azure
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ryan Spagnola 2017-09-29 13:06:12 UTC
Description of problem:
When provisioning through Azure portal an option to not have a public IP address is there and we would expect the same behavior through the CloudForms portal.  If this is not available automatically is there a miq_provision.set_option  available that we can use to set this?

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

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Looks like it isnt required: https://github.com/ManageIQ/manageiq-providers-azure/blob/master/content/miq_dialogs/miq_provision_azure_dialogs_template.yaml#L184 [1]
Do you know if its a required field in the UI? As shown in the link above that we can change the dialogs to true or false. If seems if you dont select a floating IP in the dialogs, we create one called <vm-name-PublicIp>

Comment 2 Greg McCullough 2017-09-29 13:23:42 UTC
Bronagh - Please review.  Let me know if we need to discuss the "set_option" comment.  Thanks.


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