Bug 1329007 - OSP8 Failed introspection , boot.ipxe connection reset
Summary: OSP8 Failed introspection , boot.ipxe connection reset
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: ipxe
Version: 8.0 (Liberty)
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Miroslav Rezanina
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-20 22:14 UTC by rlopez
Modified: 2019-12-16 05:41 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-08 14:10:52 UTC
Target Upstream Version:


Attachments (Terms of Use)
Screen of what I'm seeing on a system during introspection. (11.49 KB, image/png)
2016-04-20 22:14 UTC, rlopez
no flags Details

Description rlopez 2016-04-20 22:14:20 UTC
Created attachment 1149212 [details]
Screen of what I'm seeing on a system during introspection.

Description of problem:
OSP8 GA is not properly introspecting. When it attempts it first says iPXE initalising devices ok, then goes off and attempts to get the boot.ipxe image but it says Connection reset, no more network devices.

I'm attaching an image of exactly what I'm seeing on one of my servers.

I'm using DELL R510s and DELL M520s. All systems are using BIOS not UEFI. Also this worked perfectly for me when I was testing OSP8 Beta 8.

How reproducible:
100%

Steps to Reproduce:
1.install undercloud
2.attempt bulk introspection

Comment 3 Dmitry Tantsur 2016-05-04 12:32:27 UTC
I wonder if it's a regression in the latest ROM..

Anyway, could you please grab /var/log/httpd/ironic_access.log and /var/log/httpd/ironic_error.log (these files may have a postfix with date, depending on when you've attempted the boot).

Comment 4 jose.lausuch 2016-06-05 09:23:24 UTC
@rlopez, did you manage to fix that? I'm seeing exactly the same problem...

Comment 5 rlopez 2016-06-06 14:18:11 UTC
@jose,

Sadly my problem was user error on my part. I had two OSP environments that I was testing with and both undercloud's were on the same OSP provisioning network. I accidentally had left one of the undercloud systems on and it was high jacking the PXE boot process thus the error. 


Roger

Comment 6 jose.lausuch 2016-06-07 07:31:07 UTC
My issue was actually the httpd service, it crashed for some reason and after bringing it up again the pxe worked fine.
Thanks!

Comment 7 Miroslav Rezanina 2016-06-08 14:10:52 UTC
(In reply to jose.lausuch from comment #6)
> My issue was actually the httpd service, it crashed for some reason and
> after bringing it up again the pxe worked fine.
> Thanks!

Ok, closing the bz as notabug


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