Bug 1877071 - vSphere IPI - Nameserver limits were exceeded, some nameservers have been omitted
Summary: vSphere IPI - Nameserver limits were exceeded, some nameservers have been omi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.7.0
Assignee: Morgan Peterman
QA Contact: Michael Nguyen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-08 19:31 UTC by Morgan Peterman
Modified: 2021-02-24 15:17 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:17:26 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 2064 0 None closed Bug 1877071: vSphere - Limit the number of nameservers to 3 2021-02-19 05:12:35 UTC
Red Hat Knowledge Base (Solution) 5385751 0 None None None 2020-09-13 16:59:52 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:17:46 UTC

Description Morgan Peterman 2020-09-08 19:31:40 UTC 
Description of problem:

When deploying using the VMware IPI method with more than 3 nameservers you see 'Nameserver limits were exceeded, some nameservers have been omitted' errors in the event logs.


Version-Release number of selected component (if applicable): 4.5 and 4.6 Nightly


How reproducible:

Every time.

Steps to Reproduce:
1. Deploy vSphere IPI using DHCP configured with 3 or more DNS servers. 

Actual results:
Error message fills up event log: Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 10.1.11.173 10.11.5.19 10.10.160.2

Expected results:
Extra DNS servers are removed by the MachineConfig Operator like they are for OpenStack and BareMetal

Additional info:
Comment 1 Scott Dodson 2020-09-09 14:37:38 UTC 
Moving the bug to align with the component the PR was filed against.
Comment 10 Yu Qi Zhang 2021-01-06 16:43:21 UTC 
This may warrant a small doc update snippet for the bug fix. Leaving to Morgan to decide
Comment 11 Morgan Peterman 2021-01-06 18:51:36 UTC 
Yu,

I don't think we should one. This is the same fix that was applied for OpenStack previously and a Docs update wasn't provided then.
Comment 12 Yu Qi Zhang 2021-01-06 19:02:14 UTC 
Sounds good. Marking No Doc Update needed
Comment 17 errata-xmlrpc 2021-02-24 15:17:26 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633
Note You need to log in before you can comment on or make changes to this bug.