New commit detected on cfme/5.5.z:
https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=e93c09f5df6e63f1b0611b8d117fe1cf710cbb7f

commit e93c09f5df6e63f1b0611b8d117fe1cf710cbb7f
Merge: ec802d9 50ced74
Author:     Greg McCullough <gmccullo@redhat.com>
AuthorDate: Mon Dec 7 13:48:39 2015 -0500
Commit:     Greg McCullough <gmccullo@redhat.com>
CommitDate: Mon Dec 7 13:48:39 2015 -0500

    Merge branch 'bugzilla_1287850_5_5_z' into '5.5.z'
    
    Use same dialog for self service user and admins
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1287850
    
    Previously we used to have separate dialogs for self service user and admin users. Going forward we will only have 1 dialog for both user and admin. If a customer needs to have separate dialog for self service users they would have to copy the dialogs and customize them.
    
    Clean Cherry Pick from https://github.com/ManageIQ/manageiq/pull/5670
    
    See merge request !581

 .../__methods__/vm_dialog_name_prefix.rb           |   2 -
 .../Profile.class/evmgroup-user_self_service.yaml  |  12 -
 .../__methods__/vm_dialog_name_prefix.rb           |   1 -
 .../Profile.class/evmgroup-user_self_service.yaml  |  12 -
 .../miq_dialogs/miq_provision_dialogs-user.yaml    | 721 -------------------
 .../miq_provision_dialogs_clone_to_template.yaml   | 721 -------------------
 .../miq_provision_dialogs_clone_to_vm.yaml         | 721 -------------------
 .../miq_provision_dialogs_template.yaml            | 762 ---------------------
 ...provision_vmware_dialogs_clone_to_template.yaml | 721 +++++++++++++++++++
 .../miq_provision_vmware_dialogs_clone_to_vm.yaml  | 721 +++++++++++++++++++
 .../miq_provision_vmware_dialogs_template.yaml     | 762 +++++++++++++++++++++
 11 files changed, 2204 insertions(+), 2952 deletions(-)

Able to provision instances for user self service roles.

Verified:5.5.2.1.20160114044944_395c086

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:0159