Bug 1330725 - Provisioning a Cloud Instance displays a phone number label but not a phone number field.
Summary: Provisioning a Cloud Instance displays a phone number label but not a phone n...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.6.0
Assignee: Greg McCullough
QA Contact: Jeff Teehan
URL:
Whiteboard: provisioning:ui:dialog
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-26 19:52 UTC by Jeff Teehan
Modified: 2016-06-29 15:55 UTC (History)
7 users (show)

Fixed In Version: 5.6.0.5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 15:55:05 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Provision Instance screenshot. (62.73 KB, image/png)
2016-04-27 22:08 UTC, Jeff Teehan
no flags Details
Requester tab with all fields visible (74.00 KB, image/png)
2016-04-28 13:27 UTC, Greg McCullough
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description Jeff Teehan 2016-04-26 19:52:34 UTC
Description of problem:
When I provision a cloud instance from an image using the LifeCycle/Provision Instances, the Request Tab contains a label and a space from Phone but not an actual html input box.

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

How reproducible:
Always

Steps to Reproduce:
1.  Navigate to Compute:Cloud:Instances
2.  Select Provision VM from the LifeCycle menu
3.  Select a template (SCVMM in my case) and click Next

Actual results:
At the Request Information there is a new phone number label, and a space for the field, but no actual field.

Expected results:
Need to display the input for phone number.

Additional info:

Comment 2 Greg McCullough 2016-04-26 22:27:37 UTC
Jeff, Can you provide a screenshot as I cannot reproduce this issue.  Also please clarify where you are seeing this.  You reference Compute:Cloud:Instances but say you are selecting a SCVMM template which is infrastructure.

Comment 3 Jeff Teehan 2016-04-27 22:08:40 UTC
Created attachment 1151647 [details]
Provision Instance screenshot.

This what it looks like on my machine.

Comment 4 Greg McCullough 2016-04-28 13:27:56 UTC
Created attachment 1151894 [details]
Requester tab with all fields visible

Thanks Jeff.

There seems to be two issues here:
1) The Azure dialogs have the phone set to ":display: :show" which should be :hide by default.  (We can fix that with this ticket)

2) All the fields hidden by default on the requester tab show the same empty box which we should open another bug ticket for the UI team.  (Attaching screenshot)

Comment 6 CFME Bot 2016-04-29 22:01:13 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/db735ced2f1ab73f705c5250aaa1fedf700e8bb9

commit db735ced2f1ab73f705c5250aaa1fedf700e8bb9
Author:     Greg McCullough <gmccullo>
AuthorDate: Thu Apr 28 09:31:58 2016 -0400
Commit:     Greg McCullough <gmccullo>
CommitDate: Thu Apr 28 09:31:58 2016 -0400

    Hide "Phone" field on Azure provision dialog by default
    
    Changed to match all other vendor dialog default values.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1330725

 product/dialogs/miq_dialogs/miq_provision_azure_dialogs_template.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 7 Greg McCullough 2016-04-29 22:08:51 UTC
Jeff - Realized after posting comment #4 that the fields should be set to 
:display: :edit      (instead of :show)

With that change all the fields work as expected.

The PR for this bug hides the field so it matches the other default dialogs.

Comment 8 Jeff Teehan 2016-05-06 18:52:57 UTC
This is fixed in 5.6.0.5 and verified using https://10.16.6.51/vm_cloud/explorer

Comment 11 errata-xmlrpc 2016-06-29 15:55:05 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, 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/RHBA-2016:1348


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