Bug 1494340

Summary: Unexpected error while editing policy of Cloud Subnets
Product: Red Hat CloudForms Management Engine Reporter: Yadnyawalk Tale <ytale>
Component: UI - OPSAssignee: Martin Povolny <mpovolny>
Status: CLOSED ERRATA QA Contact: Yadnyawalk Tale <ytale>
Severity: medium Docs Contact:
Priority: high    
Version: unspecifiedCC: cpelland, hkataria, jhardy, mpovolny, obarenbo, simaishi
Target Milestone: GAFlags: ytale: automate_bug-
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui:policy
Fixed In Version: 5.9.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-01 13:18:06 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:

Description Yadnyawalk Tale 2017-09-22 05:30:56 UTC
Created attachment 1329366 [details]
screenshot

Description of problem:


Version-Release number of selected component (if applicable):
[UPSTREAM]fine-3.20170808115538_09b4f87


How reproducible:


Steps to Reproduce:
1. Add cloud provider first (Openstack RHOS7-GA recommended)
2. Navigate to Compute -> Cloud -> Tenants
3. Click on 'admin' from 'Cloud Tenants' table
4. Click on 'Cloud Subnets' from 'Relationship' table
5. Click on one 'Cloud Subnets' from 'All Images' table
6. From 'Policy' select 'Edit tag'


Actual results:


Expected results:


Additional info:

Comment 4 Martin Povolny 2017-09-27 11:14:08 UTC
*** Bug 1486682 has been marked as a duplicate of this bug. ***

Comment 6 Yadnyawalk Tale 2017-11-10 09:13:02 UTC
Hey Martin,

I can able to navigate 'edit tags' now. (but im still getting unexpected error after selecting tag category or assigned value, I had raised separate BZ1511815 for that). Verifying this but need to fix mentioned behavior too.

Verified on: 5.9.0.7.20171107212356_ed87902

Thanks!

Comment 9 errata-xmlrpc 2018-03-01 13:18:06 UTC
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-2018:0380