Created attachment 1471326 [details] demo Description of problem: Smart management tags can't be set to any of the container's provider, after selecting an object to tag and navigating to Edit tags page, when selecting a category an exception is raised. Version-Release number of selected component (if applicable): 5.9.4 How reproducible: 100% Steps to Reproduce: 1. Select any container's provider object to tag (navigate to the object details page) 2. On the upper toolbar select "Policy --> Edit tags" 3. Select a random category for the new tag Actual results: An exception is raised, impossible to add a tag using the GUI Expected results: The second dropdown list (the one for the tag itself) has to be load with all the available tags for the selected category. A tag can be selected and the save option needs to be available. After saving the tag info, auto navigation to the selected object details page should occur and flash message should appear with info about the new tag that just was set. Additional info: See attached demo
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 the severity to Low.
I'm unable to reproduce the described problem: master, gaprindashvili, 5.9.4 appliance. Is there perhaps a running appliance showing this bug? Thanks.
Created attachment 1474024 [details] demo
Created attachment 1474025 [details] error_msg
jprause: what's the question you're asking here?
The traceback from comment #10 has been fixed in https://github.com/ManageIQ/manageiq-ui-classic/pull/4450 I'm moving this over to POST, should we need to backport this to 5.9 or 5.10.
Verified in 5.11.0.23.20190904213640_d113674 Assign a tag to various container objects and verified no mention of "csp-report" in any of the appliance's logs
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. https://access.redhat.com/errata/RHBA-2019:4199