Bug 1257783 - Connection reset by peer during Ironic provisioning
Summary: Connection reset by peer during Ironic provisioning
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 5.0 (RHEL 7)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 10.0 (Newton)
Assignee: Lucas Alvares Gomes
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-28 03:26 UTC by Gaëtan Trellu
Modified: 2016-08-22 16:31 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-22 16:31:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Connection reset by peer. (101.43 KB, image/jpeg)
2015-08-28 03:29 UTC, Gaëtan Trellu
no flags Details

Description Gaëtan Trellu 2015-08-28 03:26:50 UTC
Description of problem:

During an overcloud deployment, sometime some Ironic nodes stay in "wait call-back" state.

After a quick jump on the IPMI console, we can see the "nc" process running but without any activity.

A little bit upper in the console, we can see a fail during the curl command:
  - Recv failure: Connection reset by peer

We just have to power cycle the node and the it pass in "Deploying -> Wait Call-back - > Deploying -> Active" state (because the curl has been performed).

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

rhos-release-0.66-1.noarch
python-rdomanager-oscplugin-0.0.8-44.el7ost.noarch
puddle images 2015-08-07.1

How reproducible:

Try to deploy an overcloud Heat stack.

Actual results:

Ironic node stay in "wait call-back" state.

Expected results:

Ironic node in "active" state.

Additional info:

Have a look on the screenshot

Comment 3 Gaëtan Trellu 2015-08-28 03:29:05 UTC
Created attachment 1067902 [details]
Connection reset by peer.

Comment 4 chris alfonso 2015-08-28 16:10:27 UTC
Lucas, would you mind validating there isn't a config issue to look into on this?

Comment 7 Mike Burns 2016-04-07 20:47:27 UTC
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 9 Lucas Alvares Gomes 2016-05-19 10:23:22 UTC
Hi,

Just to confirm, was this bug found in osp 7 right? Cause using "nc" was an old behavior with the previous deploy ramdisk which has been replaced for osp8+.

Can you re validate it please?

Comment 10 Gaëtan Trellu 2016-06-15 15:03:03 UTC
Hi,

No more issues in OSP-d 8.x

Gaetan

Comment 12 Lucas Alvares Gomes 2016-08-22 16:31:27 UTC
(In reply to Gaëtan Trellu from comment #10)
> Hi,
> 
> No more issues in OSP-d 8.x
> 
> Gaetan

Thanks!

Closing this bug because we already got rid of the old bash ramdisk osp 8+


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