Bug 1503287

Summary: [Embedded Ansible] Service provisioned through Ansible Playbook Button is not visible under /service/explorer Active Services
Product: Red Hat CloudForms Management Engine Reporter: Kedar Kulkarni <kkulkarn>
Component: UI - ServiceAssignee: Allen W <awight>
Status: CLOSED CURRENTRELEASE QA Contact: Kedar Kulkarni <kkulkarn>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.0CC: cpelland, dclarizi, dmisharo, gmccullo, hkataria, jhardy, kkulkarn, lcouzens, mkanoor, mpovolny, obarenbo, pakotvan, simaishi, tfitzger
Target Milestone: GAKeywords: TestOnly
Target Release: 5.9.0Flags: kkulkarn: automate_bug-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.9.0.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-06 14:53:01 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:
Bug Depends On: 1506796    
Bug Blocks:    

Description Kedar Kulkarni 2017-10-17 18:28:41 UTC
Description of problem:
If you create a custom VM/Instance button that runs an ansible playbook, the Service that is provisioned during that transaction is not visible in "Active Services" under /service/explorer in OPS UI. 


Version-Release number of selected component (if applicable):
CFME 5.9.0.2 and ManageIQ master.20171017060846_05c1495

How reproducible:
Believe 100%

Steps to Reproduce:
1.Enable Embedded Ansible Role
2.Add a new Ansible Repository
3.Add appropriate credentials for the machine that you are planning on using 
4.Create a Catalog Item of type Ansible Playbook
5.Create a custom button and make it use the Ansible Playbook Catalog Item created in step 4. 
6.Navigate to Compute->Infrastructure->Virtual Machines, and select a VM
7.Click on custom button to launch the service provisioning

Actual results:
The Service that is provisioned during that transaction is not visible in "Active Services" under /service/explorer in OPS UI. 

Expected results:
Service should be visible in the OPS UI. 

Additional info:
Service is visible in Service UI under My Services.

Comment 3 Greg McCullough 2017-10-17 22:43:46 UTC
Please check that the Catalog Item has the "Display in Catalog" option selected, this controls the visibility of the item in the catalog to order as well as the resulting Service.

Comment 4 Kedar Kulkarni 2017-10-18 15:11:46 UTC
Greg, I could not select the "Display in Catalog" due to https://bugzilla.redhat.com/show_bug.cgi?id=1501528

But, if the "Display in Catalog" is set to OFF, then two things:
1) Does service show up in SSUI? Is it supposed to show up? - Currently I can see the service in SSUI
2) Does service show up in OPS UI? Is it supposed to show up? - I cannot see it in OPS UI. 

Should there be a consistency, as in should it show up in both the UI or not show up in both the UI? Just trying to understand why it shows up in one UI and not in other.

Thanks,
KK.

Comment 5 Greg McCullough 2017-10-18 17:47:31 UTC
Kedar - The Service model has a boolean "display" column which should be used to control the visibility of services in both the Ops and SSUI and I would expect them to behave the same way.

Sending to the ServiceUI team to evaluate.

Comment 6 Chris Kacerguis 2017-10-18 18:51:35 UTC
From what I read...the service IS visible in the Service UI, but it not visible in the Ops UI (and should be)...sending to the Ops UI team.

That said, we display what comes back from the API, so IF it should not be displayed, then the API team would need to change.

Comment 7 Greg McCullough 2017-10-18 19:42:10 UTC
Chris - From comment #4 "But, if the "Display in Catalog" is set to OFF, then two things..."

While it is not completely clear this would mean the resulting service would have the display property set to false.

My understanding is that the API would still return these service unless your call filtered them out.

This still appears to be an inconsistency in the Service UI.

Comment 8 Chris Kacerguis 2017-10-18 20:38:13 UTC
...missed that.  Taking ticket back.

Comment 9 Allen W 2017-10-19 16:28:03 UTC
👀 diggin' in! 🕳

Comment 10 Allen W 2017-10-19 17:34:13 UTC
@Kedar, SUPER AWESOME FIND! Yeah SUI wasn't giving display:true/false any mind so this applied to all services not just ansible ones, heres da fix! 

https://github.com/ManageIQ/manageiq-ui-service/pull/1112

Comment 11 Kedar Kulkarni 2017-10-19 17:36:23 UTC
(In reply to Allen W from comment #10)
> @Kedar, SUPER AWESOME FIND! Yeah SUI wasn't giving display:true/false any
> mind so this applied to all services not just ansible ones, heres da fix! 
> 
> https://github.com/ManageIQ/manageiq-ui-service/pull/1112

Allen, Thanks. Glad we found it before customers! :) Thanks for fixin it

Comment 12 Kedar Kulkarni 2017-11-03 16:07:34 UTC
verified on 5.9.0.5