Bug 1665284
Summary: | Tagging: Unable to edit tag from container provider page | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | John Dupuy <jdupuy> | ||||
Component: | UI - OPS | Assignee: | Hilda Stastna <hstastna> | ||||
Status: | CLOSED ERRATA | QA Contact: | John Dupuy <jdupuy> | ||||
Severity: | medium | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> | ||||
Priority: | high | ||||||
Version: | 5.9.7 | CC: | bmidwood, dmetzger, hkataria, jdupuy, lavenel, mpovolny, obarenbo, simaishi | ||||
Target Milestone: | GA | Keywords: | ZStream | ||||
Target Release: | 5.9.8 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | 5.9.8.0 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-02-12 13:58:53 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | CFME Core | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
John Dupuy
2019-01-10 21:00:27 UTC
Note: I've found that the same problem is also with any Infra provider, not just container one. Tagging Cloud Providers works well. Wanted to make a note for this bug, this is seen when you are on the Dashboard view. It works on the Summary view Verified in 5.9.8.0.20190121201402_b1df4c2. Steps for verification: 1. Add a containers provider 2. Click Compute->Containers->Providers 3. Click on the containers provider 4. Click "Policy" -> "Edit tags" from the "Dashboard" view Verified that the edit tags page shows up properly. Also verified that it displays properly from the "Summary" view. Also verified that editing the tags works for an infrastructure provider from both the "Dashboard" and "Summary" view. 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-2019:0315 |