yahoo-eng-team team mailing list archive

Thread
Date

[Bug 2095195] [NEW] VM fails to receive IPv4 from DHCP agent because the agent has not updated the network config for dnsmasq after port was created

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Ihar Hrachyshka <2095195@xxxxxxxxxxxxxxxxxx>
Date: Fri, 17 Jan 2025 18:55:45 -0000
Reply-to: Bug 2095195 <2095195@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx

Public bug reported:

https://a77b0ced621f6962ba5d-521ddb5b4802ca7b9a58415e487c1c51.ssl.cf5.rackcdn.com/927216/11/check/neutron-
ovs-tempest-dvr-ha-multinode-full/0d9ec5f/testr_results.html

In console, we see:

Starting network: dhcpcd-9.4.1 starting
DUID 00:04:5a:c9:ab:dc:5b:74:4e:f2:87:a2:fe:bd:cd:b2:08:d7
eth0: waiting for carrier
eth0: carrier acquired
eth0: IAID 3e:ed:5e:1e
eth0: adding address fe80::f816:3eff:feed:5e1e
eth0: soliciting a DHCP lease
eth0: soliciting an IPv6 router
eth0: no IPv6 Routers available
timed out
forked to background, child pid 250
OK
checking http://169.254.169.254/2009-04-04/instance-id
failed 1/20: up 202.33. request failed
failed 2/20: up 204.65. request failed
failed 3/20: up 206.97. request failed
failed 4/20: up 209.26. request failed
failed 5/20: up 211.50. request failed
failed 6/20: up 213.73. request failed

It failed to set a IPv4 address from DHCPv4. When we look for the MAC
address of the port in dhcp agent, we see:

Jan 16 00:02:40.960513 np0039580125 dnsmasq-dhcp[98161]: DHCPDISCOVER(tap0627c753-23) fa:16:3e:ed:5e:1e no address available

The port was created ~00:02:10. The last time dnsmasq was reloading its
config is:

Jan 16 00:00:58.801688 np0039580125 dnsmasq-dhcp[98161]: read
/opt/stack/data/neutron/dhcp/622cf8a2-e024-4f11-b323-ec2ed13374ce/opts

So something made the agent not update its lease info when port was
created; or neutron-server hasn't informed the agent that this port
should be configured for dhcp.

** Affects: neutron
Importance: Undecided
Status: New

** Tags: gate-failure l3-ipam-dhcp ovs

** Tags added: gate-failure l3-ipam-dhcp ovs

--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2095195

Title:
VM fails to receive IPv4 from DHCP agent because the agent has not
updated the network config for dnsmasq after port was created

Status in neutron:
New

Bug description:
https://a77b0ced621f6962ba5d-521ddb5b4802ca7b9a58415e487c1c51.ssl.cf5.rackcdn.com/927216/11/check/neutron-
ovs-tempest-dvr-ha-multinode-full/0d9ec5f/testr_results.html

In console, we see:

It failed to set a IPv4 address from DHCPv4. When we look for the MAC
address of the port in dhcp agent, we see:

Jan 16 00:02:40.960513 np0039580125 dnsmasq-dhcp[98161]: DHCPDISCOVER(tap0627c753-23) fa:16:3e:ed:5e:1e no address available

The port was created ~00:02:10. The last time dnsmasq was reloading
its config is:

Jan 16 00:00:58.801688 np0039580125 dnsmasq-dhcp[98161]: read
/opt/stack/data/neutron/dhcp/622cf8a2-e024-4f11-b323-ec2ed13374ce/opts

So something made the agent not update its lease info when port was
created; or neutron-server hasn't informed the agent that this port
should be configured for dhcp.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2095195/+subscriptions