Bug 1368168

Summary:	Editing RHEVM has default API Port 5000 in UI even though no port was set when creaing
Product:	Red Hat CloudForms Management Engine	Reporter:	John Prause <jprause>
Component:	UI - OPS	Assignee:	lgalis
Status:	CLOSED ERRATA	QA Contact:	Ilanit Stein <istein>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.6.0	CC:	adahms, cpelland, dajohnso, dclarizi, gblomqui, hkataria, jhardy, jocarter, mfeifer, mmojzis, mpovolny, obarenbo, oourfali, simaishi
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.6.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ui:provider:rhevm
Fixed In Version:	5.6.2.0	Doc Type:	Bug Fix
Doc Text:	This update resolves an issue where the default value for the OpenStack API port would be reflected in the configuration of Red Hat Enterprise Virtualization providers, causing an API Port value of '5000' to be displayed even when no port was specified during creation of that provider.	Story Points:	---
Clone Of:	1361258	Environment:
Last Closed:	2016-10-04 14:31:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	RHEVM	Target Upstream Version:
Embargoed:
Bug Depends On:	1361258
Bug Blocks:

Comment 2 Ilanit Stein 2016-09-15 08:20:57 UTC

Verified on:
CFME-5.6.2.0.20160913114355_70e9086
RHV-4.0.3-0.1.el7ev

1) Added rhevm provider with port blank. (In summary is API Port blank)
2) Edited rhevm provider to another IP address & password.
3) API Port field was empty, and I left it that way.
4) validate for the new values was successful.
5) Save of the data successful as well.
6) Refresh for the new setup data was displayed OK.

** Not sure this bug addresses the attached Red Hat Customer Portal case ID 01671420.
This case seem more related to bug 1370208, where it is also attached.

Comment 4 errata-xmlrpc 2016-10-04 14:31: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://rhn.redhat.com/errata/RHSA-2016-1996.html