Bug 1568073

Summary: Custom service attribute does not show in the ops UI
Product: Red Hat CloudForms Management Engine Reporter: ldomb
Component: UI - OPSAssignee: lgalis
Status: CLOSED ERRATA QA Contact: Niyaz Akhtar Ansari <nansari>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.0CC: cpelland, hkataria, jmarc, kmorey, lavenel, ldomb, lgalis, mpovolny, mshriver, obarenbo, pmcgowan, simaishi
Target Milestone: GA   
Target Release: 5.10.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-07 23:01:41 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:
Description Flags
Custom attributes none

Description ldomb 2018-04-16 17:33:26 UTC
Created attachment 1422655 [details]
Custom attributes

Description of problem:

Custom service attributes disappeared from the UI, worked in earlier versions. 

This bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1481547 fixed the extension for custom attributes. They showed up in the UI as you can see in the attachment. 

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

How reproducible:

Steps to Reproduce:
1. make the following request

curl -u admin:smartvm -O -k -v -X POST \

-H "Resource:" \

-H 'Content-Type: text/json; charset=utf8' \

-d @- << EOF


        "action": "add",

        "resources": [{

                "name": "ca1",

                "value": "value 1"

        }, {

                "name": "ca2",

                "value": "value2"




Actual results:

Item gets added but does not show up in the service UI

Expected results:

Shows up as in the attachment

Additional info:

Comment 11 Niyaz Akhtar Ansari 2019-01-21 19:23:22 UTC
I am able to see service attributes.
Verified in Version

Comment 13 errata-xmlrpc 2019-02-07 23:01:41 UTC
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.