Bug 1548568

Summary: [Embedded Ansible] Request details page do not show machine credentials though selected in Dialog
Product: Red Hat CloudForms Management Engine Reporter: Kedar Kulkarni <kkulkarn>
Component: AutomateAssignee: Greg McCullough <gmccullo>
Status: CLOSED NOTABUG QA Contact: Kedar Kulkarni <kkulkarn>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.0CC: cpelland, gmccullo, hkataria, kkulkarn, lavenel, mkanoor, mpovolny, obarenbo, simaishi, tfitzger
Target Milestone: GAKeywords: Regression
Target Release: cfme-futureFlags: kkulkarn: automate_bug-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ansible_embed
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-19 21:37:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kedar Kulkarni 2018-02-23 21:48:49 UTC 
Description of problem:
In the request details for Ansible Playbook service request, Credentials are shown to be <None> instead of actual credentials that are being used though selected in Dialog at the time of ordering.

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

How reproducible:
Believe 100%

Steps to Reproduce:
1.Enable Embedded ansible role.
2.Add repository and machine credentials. 
3.Create a catalog item with some credentials
4.Order service with some other credentials
5.See Request details for the service you just ordered, Credentials section shows "<None>".

Actual results:
Even though you have selected the credentials in dialog at the time of ordering the service request details shows "<None>"

Expected results:
Request details should show which credentials are being used instead of saying "<None>"

Additional info:
Comment 2 Kedar Kulkarni 2018-02-23 22:04:04 UTC 
Worked until 5.9.0.21. As well as in 5.8.3.4.
Comment 4 Greg McCullough 2018-02-26 16:25:22 UTC 
Seems like the root cause is reported in bug 1548562.  This bug should likely be marked as a duplicate.
Comment 6 Greg McCullough 2018-04-12 12:17:42 UTC 
Kedar - Can you retest and confirm this is fixed with the latest build?
Comment 7 Kedar Kulkarni 2018-04-12 14:49:05 UTC 
Hey Greg, can you provide build number or some clue to make sure I look at correct build?
Comment 8 Greg McCullough 2018-04-12 15:17:13 UTC 
The suggested duplicate in comment #4 has a 5.9.1 BZ https://bugzilla.redhat.com/show_bug.cgi?id=1553484 which is already marked "CLOSED ERRATA".

I would like this validated against 5.9.1 release build.
Comment 10 Tina Fitzgerald 2018-04-19 21:37:38 UTC 
Hi Kedar,

Closing this ticket since the Request details shows the credentials.

We should track the credentials being consistent issue separately.

Thanks,
Tina
Comment 11 Kedar Kulkarni 2018-04-20 16:46:22 UTC 
@Tina,
Actually this seems to be consistent in 5.9.2.2
Comment 12 Tina Fitzgerald 2018-04-20 18:22:39 UTC 
Hi Kedar,

That's great news.

Thanks,
Tina