Bug 1390643

Summary:	[Beta 1] adding RSA to OpenStack Director fails to verify credentials
Product:	Red Hat CloudForms Management Engine	Reporter:	Loic Avenel <lavenel>
Component:	Providers	Assignee:	Sam Lucidi <slucidi>
Status:	CLOSED NOTABUG	QA Contact:	Mike Foley <mfoley>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	5.7.0	CC:	jfrey, jhardy, lavenel, mhild, obarenbo, vestival
Target Milestone:	GA
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-09 13:49:37 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:

Description Loic Avenel 2016-11-01 15:16:01 UTC

Description of problem: When adding RSA to OpenStack Director fails to verify credentials with undefined method `verify_credentials' 


Version-Release number of selected component (if applicable): 5.7.0.7-beta1.20161025153249_9376fbd


How reproducible: always


Steps to Reproduce:
1. add a OpenStack Director
2. add default credentials: and validate.. works ok 
3. add RSA credentials and validate... it fails

Actual results:

[----] W, [2016-11-01T10:59:58.356287 #30420:15003ec]  WARN -- : MIQ(ManageIQ::Providers::Openstack::InfraManager#authentication_check_no_validation) type: ["ssh_keypair"] for [99000000000008] [OSP-d] Validation failed: error, undefined method `verify_credentials' for nil:NilClass


Expected results:


Additional info:

Comment 2 Marcel Hild 2016-11-08 16:28:23 UTC

I can't even reproduce this. 
I successfully added a OpenStack Infra provider with valid credentials and with RSA Key Pair.

First method:
* new Openstack Provider
* verify credentials -> ok
* RSA Tab: add name / key
* go back to default (because no validate button present)
* verfiy credentials -> ok
* Add Provider

Second method
* new Openstack Provider
* verify credentials -> ok
* Add Provider
* edit provider
* RSA Tab: add name / key
* Add Provider
* Edit Provider
* RSA Tab: verify credentials -> ok

Comment 3 Sam Lucidi 2016-11-08 16:45:00 UTC

I have similarly not been able to reproduce this, when adding a new provider or when editing an existing one. Loic, do you have any more information about the circumstances in which this occurs?

Comment 4 Loic Avenel 2016-11-08 18:29:26 UTC

(In reply to Marcel Hild from comment #2)
> I can't even reproduce this. 
> I successfully added a OpenStack Infra provider with valid credentials and
> with RSA Key Pair.
> 
> First method:
> * new Openstack Provider
> * verify credentials -> ok
> * RSA Tab: add name / key
> * go back to default (because no validate button present)
> * verfiy credentials -> ok
> * Add Provider
> 
> Second method
> * new Openstack Provider
> * verify credentials -> ok
> * Add Provider
> * edit provider
> * RSA Tab: add name / key
> * Add Provider
> * Edit Provider
> * RSA Tab: verify credentials -> ok

It may be an environment issue or a bad credentials files.. I have same issue wit 4.1
if it does work for you we can then close it.

Comment 5 Loic Avenel 2016-11-09 10:21:02 UTC

(In reply to Loic Avenel from comment #4)
> (In reply to Marcel Hild from comment #2)
> > I can't even reproduce this. 
> > I successfully added a OpenStack Infra provider with valid credentials and
> > with RSA Key Pair.
> > 
> > First method:
> > * new Openstack Provider
> > * verify credentials -> ok
> > * RSA Tab: add name / key
> > * go back to default (because no validate button present)
> > * verfiy credentials -> ok
> > * Add Provider
> > 
> > Second method
> > * new Openstack Provider
> > * verify credentials -> ok
> > * Add Provider
> > * edit provider
> > * RSA Tab: add name / key
> > * Add Provider
> > * Edit Provider
> > * RSA Tab: verify credentials -> ok
> 
> It may be an environment issue or a bad credentials files.. I have same
> issue wit 4.1
> if it does work for you we can then close it.

I just tested it with Nightly build and it worked fine. I can be closed.