Bug 1479412 - Smart Management tag fail to set on Container object
Summary: Smart Management tag fail to set on Container object
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.8.2
Assignee: zakiva
QA Contact: Shalom Naim
URL:
Whiteboard: container
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-08 14:20 UTC by Shalom Naim
Modified: 2018-01-05 23:51 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-04 09:10:30 UTC
Category: ---
Cloudforms Team: Container Management
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
reproduce of the bug (3.38 MB, application/octet-stream)
2017-08-08 14:20 UTC, Shalom Naim
no flags Details
System's log (5.27 MB, text/plain)
2017-08-08 14:24 UTC, Shalom Naim
no flags Details

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.


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