Bug 1325483 - dnsmasq does not pxe boot
Summary: dnsmasq does not pxe boot
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic-inspector
Version: 8.0 (Liberty)
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Dmitry Tantsur
QA Contact: Raviv Bar-Tal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-09 06:08 UTC by Jaison Raju
Modified: 2016-10-31 12:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-31 12:07:47 UTC
Target Upstream Version:


Attachments (Terms of Use)
Working Dell pxe legacy pcap (980.77 KB, application/octet-stream)
2016-04-14 11:31 UTC, Jaison Raju
no flags Details
Working Dell pxe legacy screenshot (27.56 KB, image/png)
2016-04-14 11:32 UTC, Jaison Raju
no flags Details
Not working IBM pxe legacy pcap (10.88 KB, application/octet-stream)
2016-04-14 11:34 UTC, Jaison Raju
no flags Details
Not working IBM pxe legacy screenshot (210.52 KB, image/png)
2016-04-14 11:35 UTC, Jaison Raju
no flags Details
Not working IBM pxe UEFI pcap (145.21 KB, application/octet-stream)
2016-04-14 11:37 UTC, Jaison Raju
no flags Details
Not working IBM pxe UEFI screenshot (212.37 KB, image/png)
2016-04-14 11:38 UTC, Jaison Raju
no flags Details

Description Jaison Raju 2016-04-09 06:08:01 UTC
Description of problem:
This has been tested for broadcom based NICs on dell-per630 &
also on ibm-x3630m4 .

Version-Release number of selected component (if applicable):
RC-1
dell-per630
ibm-x3630m4
openstack-ironic-inspector-2.2.5-2.el7ost.noarch.rpm
dnsmasq-2.66-14.el7_1.x86_64.rpm (@rhel-7-server-rpms_
dnsmasq-utils-2.66-14.el7_1.x86_64.rpm (rhel-7-server-openstack-8-rpms)
python-ironic-inspector-client-1.2.0-6.el7ost.noarch.rpm
How reproducible:
Always

Steps to Reproduce:
1. Add require repositories 
2. install undercloud packages .
3. copy / modify undercloud.conf
4. undercloud install
5. Introspect

Actual results:
PXEclient fails to get IP address .

Expected results:


Additional info:
The dhcp request reaches namespace & dnsmasq process but does not service or respond back .
PFA:
Screenshot of pxeclient.
tcpdump - No option 175 . I tried using option 60 also , but didnt work .
strace - Indicates that the dhcp discover packet is parsed .
Yet to test this hardware on RHOS7 .
Another descripancy i notice is that dnsmasq is missin in osp channel

Comment 7 Jaison Raju 2016-04-14 11:31:11 UTC
Created attachment 1147176 [details]
Working Dell pxe legacy pcap

Comment 8 Jaison Raju 2016-04-14 11:32:27 UTC
Created attachment 1147188 [details]
Working Dell pxe legacy screenshot

Comment 9 Jaison Raju 2016-04-14 11:34:03 UTC
Created attachment 1147191 [details]
Not working IBM pxe legacy pcap

Comment 10 Jaison Raju 2016-04-14 11:35:22 UTC
Created attachment 1147193 [details]
Not working IBM pxe legacy screenshot

Comment 11 Jaison Raju 2016-04-14 11:37:52 UTC
Created attachment 1147195 [details]
Not working IBM pxe UEFI pcap

Comment 12 Jaison Raju 2016-04-14 11:38:43 UTC
Created attachment 1147196 [details]
Not working IBM pxe UEFI screenshot

Comment 14 Jaison Raju 2016-04-16 16:27:41 UTC
Hi ,

Looks like i didn't do a thorough research on this issue .
Seems like we already have a bz opened & it is specific to intel i350cards:
https://bugzilla.redhat.com/show_bug.cgi?id=1267030
Which are the nics used over here .

I will test the workaround by using latest http://boot.ipxe.org/undionly.kpxe .
I will close this bz if the workaround does fix the issue , assuming that
both these bugs are same .

Regards,
Jaison R

Comment 15 Dmitry Tantsur 2016-10-31 11:09:26 UTC
> I will test the workaround by using latest http://boot.ipxe.org/undionly.kpxe 

Has it worked for you?

Comment 16 Jaison Raju 2016-10-31 12:07:47 UTC
(In reply to Dmitry Tantsur from comment #15)
> > I will test the workaround by using latest http://boot.ipxe.org/undionly.kpxe 
> 
> Has it worked for you?

Yes, If fact i didnt need to try the upstream file . I am just using latest repo.
I will test again to confirm on the same hardware once it is free in 2-3weeks.
We can close this bug now .

Regards,
Jaison R


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