Bug 1257783 - Connection reset by peer during Ironic provisioning
Connection reset by peer during Ironic provisioning
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director (Show other bugs)
5.0 (RHEL 7)
x86_64 Linux
medium Severity medium
: ---
: 10.0 (Newton)
Assigned To: Lucas Alvares Gomes
Shai Revivo
Depends On:
  Show dependency treegraph
Reported: 2015-08-27 23:26 EDT by Gaëtan Trellu
Modified: 2016-08-22 12:31 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-08-22 12:31:27 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

  None (edit)
Description Gaëtan Trellu 2015-08-27 23:26:50 EDT
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):

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-27 23:29:05 EDT
Created attachment 1067902 [details]
Connection reset by peer.
Comment 4 chris alfonso 2015-08-28 12:10:27 EDT
Lucas, would you mind validating there isn't a config issue to look into on this?
Comment 7 Mike Burns 2016-04-07 16:47:27 EDT
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 06:23:22 EDT

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 11:03:03 EDT

No more issues in OSP-d 8.x

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


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.