Description of problem: In 5.8 only email info was left as mandatory field on Request Tab during Instance provision, but this update was missed on Azure. EC2/GCE require only email input, but Azure also needs First/Last name Version-Release number of selected component (if applicable):5.8. How reproducible:100% Steps to Reproduce: 1.Provision Instance on Azure without First/Last name Actual results:warning message Expected results:these fields should not be mandatory Additional info:Does azure have special limitations on this?
No difference for Azure. This dialog was missed before it was the only provision dialog moved into a separate repo which explains why it was not changed. Billy - Please clone and fork the manageiq-providers-azure and provide the same dialog change you did for https://github.com/ManageIQ/manageiq/pull/14694.
https://github.com/ManageIQ/manageiq-providers-azure/pull/73
New commit detected on ManageIQ/manageiq-providers-azure/master: https://github.com/ManageIQ/manageiq-providers-azure/commit/dcea66150a685374ccb967cec75e3795bc66daa1 commit dcea66150a685374ccb967cec75e3795bc66daa1 Author: william fitzgerald <wfitzger> AuthorDate: Mon May 22 13:47:05 2017 -0400 Commit: william fitzgerald <wfitzger> CommitDate: Mon May 22 13:47:05 2017 -0400 Automate - Azure - Provisioning First and Last name are no longer required. Fields are not being populate during life-cycle provisioning so There is no reason to make them required. This eliminates 2 required fields when provisioning. https://bugzilla.redhat.com/show_bug.cgi?id=1454351 I did this previously in ManageIQ, see https://github.com/ManageIQ/manageiq/pull/14694 @miq-bot add_label bug, content/miq_dialogs/miq_provision_azure_dialogs_template.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)