Bug 1441419

Summary: service visible in UI even when display attribute is set to false
Product: Red Hat CloudForms Management Engine Reporter: Martin Kourim <mkourim>
Component: UI - OPSAssignee: Dan Clarizio <dclarizi>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: high    
Version: 5.8.0CC: dajohnso, hkataria, jhardy, lgalis, mkourim, mpovolny, obarenbo, sshveta, twade
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: api:rest:service
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-16 21:32:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:

Description Martin Kourim 2017-04-11 21:54:03 UTC 
Description of problem:
When service is created using REST API, the "display" attribute is set to false by default. Such service should not be displayed in UI in "My Services".

In case of the reported version, when the service is created, it is visible in UI (after reload) even though the "display" attribute is set to false.


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


How reproducible:
Very


Steps to Reproduce:
1. Create a service
POST /api/services
{
  "action": "create",
  "resources": [
    {"name": "test_rest_1", "description": "test service 1"}
  ]
}

2. Check that the "display" attribute is set to false
GET /api/services/:id
...
"display": false,
...

3. Reload the "My Services" page


Actual results:
The newly created service is listed in "My Services".


Expected results:
The newly created service is not listed in "My Services".
Comment 2 Tim Wade 2017-04-12 22:24:17 UTC 
This is listed as an API bug, however in your description it seems clear that the API is giving the expected response.

Are you referring to the service UI or the classic UI? This bug may be better characterized as belonging to the corresponding front end component.
Comment 3 Martin Kourim 2017-04-20 14:23:55 UTC 
Changed component to classic UI as suggested by Tim Wade.