Bug 1471146

Summary: Unexpected error encountered while provider editing
Product: Red Hat CloudForms Management Engine Reporter: Nikhil Dhandre <ndhandre>
Component: UI - OPSAssignee: Sam Lucidi <slucidi>
Status: CLOSED ERRATA QA Contact: Ola Pavlenko <opavlenk>
Severity: high Docs Contact:
Priority: high    
Version: 5.8.0CC: dajohnso, hkataria, jhardy, mpovolny, ndhandre, obarenbo, simaishi, slucidi, tzumainn
Target Milestone: GAKeywords: Reopened
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: openstack
Fixed In Version: 5.9.0.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-01 13:15:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Openstack Target Upstream Version:
Embargoed:
Attachments:
Description Flags
unexpected error video none

Description Nikhil Dhandre 2017-07-14 14:01:30 UTC
Created attachment 1298358 [details]
unexpected error video

Description of problem:
while editing cloud provider rhos7 changes causes the Unexpected error.


Version-Release number of selected component (if applicable):


How reproducible: 100% 


Steps to Reproduce:
1. Add rhos7-ga provider with proper credentials
2. Edit cloud provider 
3. Tenant Mapping Enable >> yes
4. Save changes
5. unexpected error
Actual results:
Unexpected error

Expected results:


Additional info:
reproducible

Comment 8 Sam Lucidi 2017-10-16 20:30:09 UTC
A pull request is available that should fix this issue. https://github.com/ManageIQ/manageiq-providers-openstack/pull/119

Comment 9 Nikhil Dhandre 2017-10-31 05:34:53 UTC
tested on Version 5.9.0.4.20171024163837_ef71ea6. After editing provider and enable 'Tenant Mapping' works fine, save successfully with the proper flash message 'Cloud Provider "rhos7-ga" was saved'.

Comment 12 errata-xmlrpc 2018-03-01 13:15:21 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