Bug 1531275

Summary:	[Azure]Provision Multiple VMs with Public IP selection options
Product:	Red Hat CloudForms Management Engine	Reporter:	Leo Khomenko <lkhomenk>
Component:	Providers	Assignee:	Daniel Berger <dberger>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Dave Johnson <dajohnso>
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.8.0	CC:	bsorota, cpelland, dberger, gblomqui, jfrey, jhardy, obarenbo, simaishi, smallamp
Target Milestone:	GA	Keywords:	TestOnly, ZStream
Target Release:	5.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.10.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1552303 1565342 (view as bug list)		Environment:
Last Closed:	2018-07-30 14:44:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	Bug
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	Azure	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1552303, 1565342

Description Leo Khomenko 2018-01-04 21:13:48 UTC

Description of problem: Based on this https://bugzilla.redhat.com/show_bug.cgi?id=1497202 approach same would be nice to have for multiple VM provision.
 Daniel Berger 
It turns out this altered the behavior of provisioning multiple VM's. When provisioning multiple VM's happens, the drop down menu for Public IP's is removed.

Previously all new VM's were given a new public IP automatically. But, because the default is "None", now no public IP is assigned to any new VM's.

We need to know how this should be handled. One option is to declare that new VM's always get a public IP assigned when provisioning 2+ VM's. Another option is to alter the UI so that at least "None" or "New" can be selected, which would govern the behavior of all provisioned VM's.


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


How reproducible:100%


Steps to Reproduce:
1.Provision 2+ Azure VMs
2.Select None - Public IP

Actual results: Public IP selection is not available, default behavior - create new IP for each VM 


Expected results: None/New options

Comment 2 Greg Blomquist 2018-01-16 15:16:42 UTC

Dan, I believe I remember you talking about this one in gitter.  Can you summarize that discussion here?

If I'm wrong, lemme know.

Also, sounds like this might be a dup of some other bug. ... if so, go ahead and just close this as a dup of the other.

Comment 3 Daniel Berger 2018-02-05 19:29:33 UTC

When provisioning a single VM, the user has a choice to set it to private, public, or to an existing public IP resource. But when provisioning multiple VM's, the user doesn't have any choice.

This isn't a dup of the other ticket, as the distinction is single vs multiple VM's. So, what we need to do is alter the UI to allow two options when provisioning multiple VM's - public or private.

Comment 4 Greg Blomquist 2018-02-22 22:58:53 UTC

Dan, work with Bronagh to get help from the UI or GM's team if necessary for updating the provisioning dialogs.

I wonder if this is a problem with provisioning in any public cloud.

Comment 5 Daniel Berger 2018-02-22 23:07:55 UTC

Greg, basically already done, just waiting on Bronagh's approval.

https://github.com/ManageIQ/manageiq-providers-azure/pull/210

Comment 6 Bronagh Sorota 2018-02-22 23:36:30 UTC

I would prefer the UI PR to be merged and the Azure provider PR to be updated. I let MartinP know this is for a 4.6.1 blocker:
https://github.com/ManageIQ/manageiq-ui-classic/pull/3459#issuecomment-367858641

Comment 7 Daniel Berger 2018-02-26 19:08:18 UTC

Current PR was merged. We'll refactor the core and UI side at a later date.

Comment 11 Dave Johnson 2018-07-30 14:44:21 UTC

Closing this as its already been verified in two z-streams and has test coverage around it.