Instances not getting DHCP IP addresses

Solution Verified - Updated -

Issue

  • When we reboot VM or spin up new VMs, they are not getting IP assigned and /var/log/messages has below errors:
Sep 24 17:30:32 root dnsmasq-dhcp[38616]: DHCPDISCOVER(tap69e033ee-9a) fa:16:3e:02:f1:7c no address available
Sep 24 17:30:33 root dnsmasq-dhcp[38616]: DHCPDISCOVER(tap69e033ee-9a) fa:16:3e:c8:e9:14 no address available
Sep 24 17:30:36 root dnsmasq-dhcp[38616]: DHCPDISCOVER(tap69e033ee-9a) fa:16:3e:78:cc:d9 no address available
Sep 24 17:30:37 root dnsmasq-dhcp[38616]: DHCPDISCOVER(tap69e033ee-9a) fa:16:3e:1d:a6:fb no address available
Sep 24 17:30:38 root dnsmasq-dhcp[38616]: DHCPDISCOVER(tap69e033ee-9a) fa:16:3e:7e:6e:4f no address available
Sep 24 17:30:38 root dnsmasq-dhcp[38616]: DHCPDISCOVER(tap69e033ee-9a) fa:16:3e:c8:e9:14 no address available
Sep 24 17:30:39 root dnsmasq-dhcp[38616]: DHCPDISCOVER(tap69e033ee-9a) fa:16:3e:25:0f:0f no address available
Sep 24 17:30:41 root dnsmasq-dhcp[38616]: DHCPDISCOVER(tap69e033ee-9a) fa:16:3e:02:f1:7c no address available
Sep 24 17:30:43 root dnsmasq-dhcp[38616]: DHCPDISCOVER(tap69e033ee-9a) fa:16:3e:5a:71:a3 no address available
Sep 24 17:30:44 root dnsmasq-dhcp[38616]: DHCPDISCOVER(tap69e033ee-9a) fa:16:3e:c8:e9:14 no address available

Environment

  • Red Hat OpenStack 4.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.