RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1214898 - RDO-dnsmasq: During attempt to deploy the overcloud, the hosts doing the PXE boot don't get IP.
Summary: RDO-dnsmasq: During attempt to deploy the overcloud, the hosts doing the PXE ...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: RDO
Classification: Community
Component: distribution
Version: Kilo
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Kilo
Assignee: RHOS Maint
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-23 19:59 UTC by Alexander Chuzhoy
Modified: 2023-04-07 11:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-08-17 14:35:02 UTC
Embargoed:


Attachments (Terms of Use)

Description Alexander Chuzhoy 2015-04-23 19:59:44 UTC
RDO-dnsmasq: During attempt to deploy the overcloud, the hosts doing the PXE boot don't get IP.

Environment:
openstack-ironic-discoverd-1.1.0-0.99.20150417.1225git.el7.centos.noarch
instack-undercloud-2.0.0-dev1655.el7.centos.noarch

Steps to reproduce:
1. Bare metal setup - install the undercloud and complete the discovery of the nodes.
2. Run "instack-deploy-overcloud --tuskar".


Result:
The creation of the overcloud gets stuck.
Checking the console of the nodes - they won't get an IP during the PXE boot.

Expected result:
The host should PXE boot normally.

Comment 1 Alexander Chuzhoy 2015-04-23 20:01:51 UTC
The content of /etc/ironic-discoverd/dnsmasq.conf used:
port=0
interface=br-ctlplane
bind-interfaces
dhcp-range=192.168.0.100,192.168.0.120,29
enable-tftp
tftp-root=/tftpboot
dhcp-boot=pxelinux.0,localhost.localdomain,192.168.0.1

Comment 2 Alexander Chuzhoy 2015-04-23 20:07:30 UTC
using tcpdump I see that the PXE booting host reaches the undercloud machine:

15:06:27.173486 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f7:79:93:ce (oui Unknown), length 548

Comment 3 Alexander Chuzhoy 2015-04-23 20:09:19 UTC
output from ps aux|grep dnsmasq:

nobody    2570  0.0  0.0  15496   408 ?        S    15:27   0:01 /sbin/dnsmasq --conf-file=/etc/ironic-discoverd/dnsmasq.conf
nobody   18051  0.0  0.0  15520   848 ?        S    15:28   0:00 dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces --interface=tap88fdd412-a4 --except-interface=lo --pid-file=/var/lib/neutron/dhcp/2c7e1812-cf50-4e8b-a633-a5f29ac16e18/pid --dhcp-hostsfile=/var/lib/neutron/dhcp/2c7e1812-cf50-4e8b-a633-a5f29ac16e18/host --addn-hosts=/var/lib/neutron/dhcp/2c7e1812-cf50-4e8b-a633-a5f29ac16e18/addn_hosts --dhcp-optsfile=/var/lib/neutron/dhcp/2c7e1812-cf50-4e8b-a633-a5f29ac16e18/opts --leasefile-ro --dhcp-authoritative --dhcp-range=set:tag0,192.168.0.0,static,86400s --dhcp-lease-max=256 --conf-file= --domain=openstacklocal


systemctl status openstack-ironic-discoverd-dnsmasq.service

openstack-ironic-discoverd-dnsmasq.service - PXE boot dnsmasq service for ironic-discoverd
   Loaded: loaded (/usr/lib/systemd/system/openstack-ironic-discoverd-dnsmasq.service; enabled)
   Active: active (running) since Thu 2015-04-23 15:27:01 EDT; 41min ago
  Process: 2000 ExecStart=/sbin/dnsmasq --conf-file=/etc/ironic-discoverd/dnsmasq.conf (code=exited, status=0/SUCCESS)
 Main PID: 2570 (dnsmasq)
   CGroup: /system.slice/openstack-ironic-discoverd-dnsmasq.service
           └─2570 /sbin/dnsmasq --conf-file=/etc/ironic-discoverd/dnsmasq.conf

Comment 4 Alexander Chuzhoy 2015-04-24 19:38:32 UTC
The issue seem to be intermittent.
Re-deployed the setup from scratch and the issue didn't re-occur.

Comment 5 Assaf Muller 2015-08-17 12:17:57 UTC
Is this still relevant?

Comment 6 Alexander Chuzhoy 2015-08-17 14:26:53 UTC
I don't reproduce it, no.
Thanks.


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