Bug 1283266

Summary: Failed to create Key Pair - ConnectionRefused
Product: Red Hat OpenStack Reporter: Ido Ovadia <iovadia>
Component: openstack-novaAssignee: Eoghan Glynn <eglynn>
Status: CLOSED DUPLICATE QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: berrange, dasmith, eglynn, kchamart, ndipanov, pbrady, sbauza, sferdjao, sgordon, vromanso, yeylon
Target Milestone: ---Keywords: Regression
Target Release: 8.0 (Liberty)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-24 16:23:39 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:

Description Ido Ovadia 2015-11-18 14:44:21 UTC
Description of problem:
=======================
Creating a Key Pair failed due to  ERROR (ConnectionRefused)


Version-Release number of selected component:
=============================================
OSP Director 8 Beta
openstack-nova-scheduler-12.0.0-1.el7ost.noarch
openstack-nova-cert-12.0.0-1.el7ost.noarch
python-nova-12.0.0-1.el7ost.noarch
openstack-nova-common-12.0.0-1.el7ost.noarch
python-novaclient-2.30.1-1.el7ost.noarch
openstack-nova-compute-12.0.0-1.el7ost.noarch
openstack-nova-api-12.0.0-1.el7ost.noarch
openstack-nova-conductor-12.0.0-1.el7ost.noarch

How reproducible:
=================
100%


Steps to Reproduce:
===================
1. Deploy undercloud (OSP Director 8 Beta)
2. Deploy overcloud HA 
3. Create a key pair: nova keypair-add test_key_18_11

Actual results:
===============
ERROR (ConnectionRefused): Unable to establish connection to http://10.19.184.221:8774/v2/df4e3a5a9d8c4e48b39826228093f2bc/os-keypairs

Expected results:
================
Key pair created successfully


Additional info:
================
Failed in Horizon to

Comment 2 Eoghan Glynn 2015-11-24 16:23:39 UTC

*** This bug has been marked as a duplicate of bug 1283265 ***