Bug 1723116 - Windows instances recieve DHCPNACK causing network issues.
Summary: Windows instances recieve DHCPNACK causing network issues.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 10.0 (Newton)
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: z13
: 10.0 (Newton)
Assignee: Nate Johnston
QA Contact: Candido Campos
URL:
Whiteboard:
Depends On: 1733527
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-22 23:34 UTC by Siggy Sigwald
Modified: 2019-10-16 09:41 UTC (History)
10 users (show)

Fixed In Version: openstack-neutron-9.4.1-46.el7ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 09:41:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3115 0 None None None 2019-10-16 09:41:36 UTC

Internal Links: 1767132

Description Siggy Sigwald 2019-06-22 23:34:37 UTC
Description of problem:
This issue is impacting only Windows instances.
1. VM client requests lease renewal every 12 hours
2. DNSmasq (DHCP Server) sends a DHCPNAK saying the lease is not found
3. Server drops connectivity briefly
4.  VM client sends REQUEST/DISCOVER and gets a reply back, and connects back with the IP address

Version-Release number of selected component (if applicable):
dnsmasq-2.76-5.el7.x86_64
dnsmasq-utils-2.76-5.el7.x86_64

Windows instance reports:
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 0x00163E09B91E.  The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server

Comment 3 Terry Wilson 2019-07-02 17:16:36 UTC
Looks like it could be https://bugs.launchpad.net/neutron/+bug/1806770 which hasn't been backported to OSP 10. Nate is investigating.

Comment 26 errata-xmlrpc 2019-10-16 09:41:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3115


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