Public bug reported: Environment: - Icehouse - multiple resource nodes - nova-network Vlan-Manager
When an instance sends out a DHCPDISCOVER or DHCPREQUEST, it sometimes leaves the resource node and gets answered by Dnsmasq running on another resource node. The remote Dnsmasq will always respond with "no address available" (to DISCOVER) or "address not available" (to REQUEST), because it doesn't have an entry for that instance in its config file. Syslog: Jan 28 15:31:04 xxxxx dnsmasq-dhcp[10454]: DHCPREQUEST(brxxx) 192.168.0.x 12:34:56:78:90:ab Jan 28 15:31:04 xxxxx dnsmasq-dhcp[10454]: DHCPNAK(brxxx) 192.168.0.x 12:34:56:78:90:ab address not available dnsmasq version 2.68 ** Affects: nova Importance: Undecided Status: New ** Tags: dhcpnak dnsmasq ** Tags added: dnsmasq ** Tags added: dhcpnak ** Description changed: Environment: - Icehouse - multiple resource nodes + - nova-network Vlan-Manager When an instance sends out a DHCPDISCOVER or DHCPREQUEST, it sometimes leaves the resource node and gets answered by Dnsmasq running on another resource node. The remote Dnsmasq will always respond with "no address available" (to DISCOVER) or "address not available" (to REQUEST), because it doesn't have an entry for that instance in its config file. Syslog: Jan 28 15:31:04 xxxxx dnsmasq-dhcp[10454]: DHCPREQUEST(br200) 192.168.0.x 12:34:56:78:90:ab Jan 28 15:31:04 xxxxx dnsmasq-dhcp[10454]: DHCPNAK(br200) 192.168.0.x 12:34:56:78:90:ab address not available ** Description changed: Environment: - Icehouse - multiple resource nodes - nova-network Vlan-Manager When an instance sends out a DHCPDISCOVER or DHCPREQUEST, it sometimes leaves the resource node and gets answered by Dnsmasq running on another resource node. The remote Dnsmasq will always respond with "no address available" (to DISCOVER) or "address not available" (to REQUEST), because it doesn't have an entry for that instance in its config file. Syslog: - Jan 28 15:31:04 xxxxx dnsmasq-dhcp[10454]: DHCPREQUEST(br200) 192.168.0.x 12:34:56:78:90:ab - Jan 28 15:31:04 xxxxx dnsmasq-dhcp[10454]: DHCPNAK(br200) 192.168.0.x 12:34:56:78:90:ab address not available + Jan 28 15:31:04 xxxxx dnsmasq-dhcp[10454]: DHCPREQUEST(brxxx) 192.168.0.x 12:34:56:78:90:ab + Jan 28 15:31:04 xxxxx dnsmasq-dhcp[10454]: DHCPNAK(brxxx) 192.168.0.x 12:34:56:78:90:ab address not available ** Description changed: Environment: - Icehouse - multiple resource nodes - nova-network Vlan-Manager When an instance sends out a DHCPDISCOVER or DHCPREQUEST, it sometimes leaves the resource node and gets answered by Dnsmasq running on another resource node. The remote Dnsmasq will always respond with "no address available" (to DISCOVER) or "address not available" (to REQUEST), because it doesn't have an entry for that instance in its config file. Syslog: Jan 28 15:31:04 xxxxx dnsmasq-dhcp[10454]: DHCPREQUEST(brxxx) 192.168.0.x 12:34:56:78:90:ab Jan 28 15:31:04 xxxxx dnsmasq-dhcp[10454]: DHCPNAK(brxxx) 192.168.0.x 12:34:56:78:90:ab address not available + + dnsmasq version 2.68 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1415592 Title: Instance DHCP Request are Sometimes Answered by Remote Dnsmasq Status in OpenStack Compute (Nova): New Bug description: Environment: - Icehouse - multiple resource nodes - nova-network Vlan-Manager When an instance sends out a DHCPDISCOVER or DHCPREQUEST, it sometimes leaves the resource node and gets answered by Dnsmasq running on another resource node. The remote Dnsmasq will always respond with "no address available" (to DISCOVER) or "address not available" (to REQUEST), because it doesn't have an entry for that instance in its config file. Syslog: Jan 28 15:31:04 xxxxx dnsmasq-dhcp[10454]: DHCPREQUEST(brxxx) 192.168.0.x 12:34:56:78:90:ab Jan 28 15:31:04 xxxxx dnsmasq-dhcp[10454]: DHCPNAK(brxxx) 192.168.0.x 12:34:56:78:90:ab address not available dnsmasq version 2.68 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1415592/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp