Bug 1283265 - Failed to create Key Pair - ConnectionRefused
Summary: Failed to create Key Pair - ConnectionRefused
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 8.0 (Liberty)
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Eoghan Glynn
QA Contact: nlevinki
URL:
Whiteboard:
: 1283266 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-18 14:43 UTC by Ido Ovadia
Modified: 2019-09-09 13:10 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-21 15:19:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ido Ovadia 2015-11-18 14:43:06 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 Dan Smith 2015-11-24 16:10:08 UTC
This probably means something is very very broken. Is nova-api even running? Can you post server logs?

I expect this is some fundamentally broken deployment thing, so I expect we should move this over to the director folks.

Comment 3 Eoghan Glynn 2015-11-24 16:23:39 UTC
*** Bug 1283266 has been marked as a duplicate of this bug. ***

Comment 4 Ido Ovadia 2015-12-13 08:59:51 UTC
(In reply to Dan Smith from comment #2)
> This probably means something is very very broken. Is nova-api even running?
> Can you post server logs?
> 
> I expect this is some fundamentally broken deployment thing, so I expect we
> should move this over to the director folks.

The setup is not available. I will try to reproduce

Comment 5 Ido Ovadia 2015-12-21 15:19:31 UTC
Not Reproduced
==============
openstack-nova-common-12.0.0-2.el7ost.noarch
openstack-nova-scheduler-12.0.0-2.el7ost.noarch
openstack-nova-conductor-12.0.0-2.el7ost.noarch
openstack-nova-cert-12.0.0-2.el7ost.noarch
python-novaclient-2.30.1-1.el7ost.noarch
python-nova-12.0.0-2.el7ost.noarch
openstack-nova-compute-12.0.0-2.el7ost.noarch
openstack-nova-api-12.0.0-2.el7ost.noarch
openstack-nova-novncproxy-12.0.0-2.el7ost.noarch
openstack-nova-console-12.0.0-2.el7ost.noarch


Note You need to log in before you can comment on or make changes to this bug.