Bug 1460696
| Summary: | HTML in node names of Control/Simulation tree | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Dmitry Misharov <dmisharo> | ||||
| Component: | UI - OPS | Assignee: | Hilda Stastna <hstastna> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Dmitry Misharov <dmisharo> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5.7.0 | CC: | hkataria, jhardy, mpovolny, obarenbo, simaishi | ||||
| Target Milestone: | GA | Keywords: | Regression, ZStream | ||||
| Target Release: | 5.7.4 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | control:ui | ||||||
| Fixed In Version: | 5.7.4.0 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-12-18 20:25:49 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | Bug | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | CFME Core | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This bug is already fixed in the newest version, but still present in 5.7.0. Maybe we need another BZ for 5.7.0 Fixed and verified in 5.7.4.0.20170913182424_63a1e18. 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/RHSA-2017:3484 |
Created attachment 1287051 [details] Screenshot of the bug Description of problem: "Scope" and "Expression" node names have html code in the names. Version-Release number of selected component (if applicable): 5.7.3.1.20170608124102_4b35a9e How reproducible: Always Steps to Reproduce: 1. Create some control vm policy with scope or expression. 2. Assign that policy to a policy profile. 3. Assign that policy profile to a provider. 4. Navigate to Control/Simulation. 5. Configure the simulation to match the policy. 6. Expand the tree. Actual results: "Scope" and "Expression" node names have html code for text coloring in the names. Expected results: "Scope" and "Expression" nodes should not contain html code for text coloring.