Bug 1441419 - service visible in UI even when display attribute is set to false
Summary: service visible in UI even when display attribute is set to false
Keywords:
Status: CLOSED DUPLICATE of bug 1444043
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: cfme-future
Assignee: Dan Clarizio
QA Contact: Dave Johnson
URL:
Whiteboard: api:rest:service
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-11 21:54 UTC by Martin Kourim
Modified: 2017-12-05 15:09 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-16 21:32:34 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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