Bug 1349607 - First and Last name are not being populated in automate during life-cycle provisoning
Summary: First and Last name are not being populated in automate during life-cycle pro...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.9.0
Assignee: William Fitzgerald
QA Contact: Shveta
URL:
Whiteboard: provision
Depends On:
Blocks: 1441270 1441423
TreeView+ depends on / blocked
 
Reported: 2016-06-23 19:11 UTC by Jared Deubel
Modified: 2020-06-11 12:54 UTC (History)
10 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1441270 1441423 (view as bug list)
Environment:
Last Closed: 2018-03-06 15:07:24 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
fields_not_populated (21.43 KB, image/png)
2016-06-23 19:12 UTC, Jared Deubel
no flags Details

Description Jared Deubel 2016-06-23 19:11:10 UTC
Description of problem:
When trying to provision a VM using the provisioning_dialogs, we are not able to populate the columns labeled: first_name and last_name. The only field that is getting populated is the e-mail field even though first_name and last_name are being set. 

Snippet from users table showing first_name and last_name set:
======================================================
-[ RECORD 1 ]----+-------------------------------------------------------------
id               | 20000000000003
name             | John Doe
email            | jdoe
icon             | 
created_on       | 2015-02-03 15:00:55.864227
updated_on       | 2016-06-23 16:00:02.832527
userid           | jdoe
settings         | ---
                 | :col_widths:
                 |   :VmOrTemplate:
                 |     name: 260
                 |     ext_management_system.name: 81
                 |     ems_cluster_name: 81
                 |     host.name: 81
                 |     ipaddresses: 81
                 |     storage.name: 81
                 |     last_compliance_status: 81
                 |     v_total_snapshots: 81
                 |     allocated_disk_storage: 81
                 |     last_scan_on: 81
                 |     region_description: 81
                 | 
filters          | ---
                 | managed:
                 | - - "/managed/owner/prod_linux"
                 | belongsto: []
                 | 
lastlogon        | 2016-06-23 15:59:07.953724
lastlogoff       | 2016-06-23 16:00:02.81456
region           | 20
current_group_id | 20000000000013
first_name       | John
last_name        | Doe
password_digest  | $2a$10$a92SyLy.CgnwFLzFtJuvN.11iciW4Rjg1Pm82B9zmyyaSXxJtryey
======================================================

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

Comment 2 Jared Deubel 2016-06-23 19:12:15 UTC
Created attachment 1171652 [details]
fields_not_populated

Comment 3 Tina Fitzgerald 2017-04-05 21:34:27 UTC
Hi Bill,

The solution for this issue is to change all of the dialog yaml files in product/dialogs/miq_dialogs to make the first and last names not required.

Thanks,
Tina

Comment 5 CFME Bot 2017-04-10 20:51:37 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/62dcdcecd50e1175893174d97c447962daab44ca

commit 62dcdcecd50e1175893174d97c447962daab44ca
Author:     william fitzgerald <wfitzger>
AuthorDate: Fri Apr 7 14:28:53 2017 -0400
Commit:     william fitzgerald <wfitzger>
CommitDate: Mon Apr 10 09:50:04 2017 -0400

    Automate - During 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=1349607

 product/dialogs/miq_dialogs/miq_host_provision_dialogs.yaml           | 4 ++--
 .../dialogs/miq_dialogs/miq_provision_amazon_dialogs_template.yaml    | 4 ++--
 .../miq_dialogs/miq_provision_configured_system_foreman_dialogs.yaml  | 4 ++--
 product/dialogs/miq_dialogs/miq_provision_dialogs.yaml                | 4 ++--
 .../dialogs/miq_dialogs/miq_provision_google_dialogs_template.yaml    | 4 ++--
 .../dialogs/miq_dialogs/miq_provision_microsoft_dialogs_template.yaml | 4 ++--
 .../dialogs/miq_dialogs/miq_provision_openstack_dialogs_template.yaml | 4 ++--
 .../dialogs/miq_dialogs/miq_provision_redhat_dialogs_clone_to_vm.yaml | 4 ++--
 .../dialogs/miq_dialogs/miq_provision_redhat_dialogs_template.yaml    | 4 ++--
 .../miq_dialogs/miq_provision_vmware_dialogs_clone_to_template.yaml   | 4 ++--
 .../dialogs/miq_dialogs/miq_provision_vmware_dialogs_clone_to_vm.yaml | 4 ++--
 .../dialogs/miq_dialogs/miq_provision_vmware_dialogs_template.yaml    | 4 ++--
 product/dialogs/miq_dialogs/vm_migrate_dialogs.yaml                   | 4 ++--
 13 files changed, 26 insertions(+), 26 deletions(-)

Comment 9 Shveta 2017-10-31 19:29:25 UTC
First name and Last name not mandatory for provisioning .
Verified in 5.9.0.4.20171024163837_ef71ea6


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