Bug 1479412

Summary: Smart Management tag fail to set on Container object
Product: Red Hat CloudForms Management Engine Reporter: Shalom Naim <snaim>
Component: UI - OPSAssignee: zakiva
Status: CLOSED WONTFIX QA Contact: Shalom Naim <snaim>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.7.0CC: bazulay, dclarizi, fsimonce, hkataria, jhardy, lavenel, mpovolny, obarenbo, snaim, zakiva
Target Milestone: GA   
Target Release: 5.8.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: container
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-04 09:10:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Container Management Target Upstream Version:
Embargoed:
Attachments:
Description Flags
reproduce of the bug
none
System's log none

Description Shalom Naim 2017-08-08 14:20:47 UTC
Created attachment 1310630 [details]
reproduce of the bug

Description of problem:
After setting smart management tag to container object the tag not visible on smart management section on container summery page 

How reproducible:
100%

Steps to Reproduce:
1. Navigate to all containers view (Compute -> Containers -> containers)
2. select random container (write down his name)
3. On the selected container summery page navigate to set tag menu (Policy -> 
   Edit tag)
4. Select random tag from the list and hit save



Actual results:
The tag is invisible on container summery page

Expected results:
The new tag have to appear on Smart Management section

Comment 2 Shalom Naim 2017-08-08 14:24:55 UTC
Created attachment 1310634 [details]
System's log

Comment 4 Dave Johnson 2017-08-09 05:43:56 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.

Comment 8 zakiva 2017-08-29 11:09:51 UTC
I couldn't reproduce this issue on both master and fine branches (and Shalom also verified it is working on a 5.8.2 appliance). 
Federico, it seems that the issue only occurs on 5.7, please let me know what we should do here.