Bug 2058030
| Summary: | On OCP 4.10+ using OVNK8s on BM IPI, nodes register as localhost.localdomain | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Denis Ollier <dollierp> | |
| Component: | Networking | Assignee: | Jaime Caamaño Ruiz <jcaamano> | |
| Networking sub component: | ovn-kubernetes | QA Contact: | Weibin Liang <weliang> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | high | CC: | aos-bugs, bgalvani, bnemec, ffernand, jcaamano, phoracek, shardy, tsedovic, vpickard, zbitter | |
| Version: | 4.10 | |||
| Target Milestone: | --- | |||
| Target Release: | 4.11.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: With OVN-Kubernetes, when setting up br-ex bridge on boot, dhcp client id and ipv6 address generation mode configuration was not being properly set.
Consequence: Unexpected IP address on br-ex on scenarios where non default dhcp client id and ipv6 address generation mode were being used.
Fix: dhcp client id and ipv6 address generation mode configuration are now being properly set on br-ex bridge..
Result: IP address on br-ex on scenarios where non default dhcp client id and ipv6 address generation mode were being used works as expected.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2069749 2070492 (view as bug list) | Environment: | ||
| Last Closed: | 2022-08-10 10:51:15 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2069749, 2070492 | |||
|
Description
Denis Ollier
2022-02-24 10:17:38 UTC
Please attach NM logs at trace level, thank you. Right, the problem is that the resolution returns "localhost,localdomain". NetworkManager uses the glibc resolver to resolve the hostname. Please check which NSS modules are installed with "grep hosts: /etc/nsswitch.conf". By default they should be: hosts: files dns myhostname meaning that first /etc/hosts is tried, then DNS, then the "myhostname" module will return the current hostname for any local address. Can you also try the following commands: getent hosts $addr getent -s dns hosts $addr dig -x $addr where $addr is the address on br-ex (e.g. 10.1.156.46). They should all give something different from "localhost.localdomain". I made a new tentative with OCP-4.11.0-0.nightly-2022-03-08-191358 and the hostname issue didn't happen (however the CSR is still not approved properly). Attaching the logs for information. Regarding the localhost issue, I noticed that it is now also happening in OCP 4.9. I managed to "bisect" that the issue has been introduced in OCP 4.9.24. The relevant changes between 4.9.23 and 4.9.24 are https://github.com/openshift/machine-config-operator/compare/b64dc344aa5a202080189abe7b1ec92bac286c06...a4fba0f500ff1fdfced1919d81253f147fea02de @jcaamano I suspect one of the backports in ovs-configure to be the cause of this issue. Okay, I've proposed a backport of the hostname fix based on https://bugzilla.redhat.com/show_bug.cgi?id=2058030#c24 . Can someone give that a /lgtm so I can chase approvers to get it merged? TIA. QE verified this bug based on https://bugzilla.redhat.com/show_bug.cgi?id=2058030#c61 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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-2022:5069 |