Bug 1334962

Summary:	Openstack creds invalid after 5.4 migration to 5.5
Product:	Red Hat CloudForms Management Engine	Reporter:	luke couzens <lcouzens>
Component:	Providers	Assignee:	Marcel Hild <mhild>
Status:	CLOSED CURRENTRELEASE	QA Contact:	luke couzens <lcouzens>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.5.0	CC:	abellott, cpelland, dajohnso, gblomqui, jfrey, jhardy, lcouzens, obarenbo
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	black:openstack:upgrade
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1368198 1368199 (view as bug list)		Environment:
Last Closed:	2016-11-21 17:49:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1368198, 1368199

Description luke couzens 2016-05-10 23:36:12 UTC

Description of problem:Openstack security protocol changes from non-ssl to ssl without validation after 5.4.5.2->5.5.4.0 migration


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


How reproducible:100%


Steps to Reproduce:
1.provision configured 5.4.5.2 appliance
2.add Openstack provider
3.Migrate to 5.5.4 using migration doc

Actual results:Provision with Openstack fails due to changes to the provider credentials


Expected results:Provision function correctly


Additional info:A quick work around is to edit the provider and change the security protocol back to non-ssl

Comment 2 Scott Seago 2016-06-08 22:09:19 UTC

Infra provider or cloud provider? Do you happen to know what the provider settings were before and after the migration?

Comment 3 luke couzens 2016-06-09 08:16:27 UTC

Hi Scott, its a cloud provider setup. Which provider settings are you after?

Comment 4 Scott Seago 2016-06-09 14:47:18 UTC

I'm mainly interested in the auth-related fields, since that's what seems to be broken post-upgrade. The upgrade script takes what's there, adds new fields, possibly changes data as needed. Post-upgrade, security protocol is wrong. Of the authentication-related fields (IP addr, port, security protocol, username, password), did anything change other than the protocol? What was the protocol before the upgrade (or is this a new field that wasn't there pre-upgrade)?

Comment 5 luke couzens 2016-06-09 18:05:15 UTC

Hey Scott, 

so before migration the provider has non-ssl set as the security protocol and after migration is complete it has changed to ssl security. That is the only thing that I have notice change, as I said editing the provider and changing the security protocol back to non-ssl it then authenticates correctly.

Hope that helps.

Comment 6 Greg Blomquist 2016-08-18 15:21:20 UTC

Assigning to Marcel to track down upgrade issues.

Comment 11 Greg Blomquist 2016-08-24 17:53:35 UTC

Luke, can you check if the same problem exists for a 5.4 -> 5.6 upgrade.  I'm assuming "yes", but just want to be sure.

Comment 13 luke couzens 2016-08-30 10:59:31 UTC

Hey Greg, this problem does exist in 5.4 -> 5.6.

cheers