Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2052098

Summary: Metal Day-1 - IPv6 Deployments with static IP fail to recognise hostname configured with rDNS
Product: Red Hat Enterprise Linux 8 Reporter: Iury Gregory Melo Ferreira <imelofer>
Component: NetworkManagerAssignee: NetworkManager Development Team <nm-team>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.4CC: augol, awolff, beth.white, bgalvani, bnemec, derekh, lmiksik, lrintel, mifiedle, nm-team, rkhan, sukulkar, till, yporagpa
Target Milestone: rcKeywords: TestBlocker
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2050296 Environment:
Last Closed: 2022-02-23 17:58:35 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:

Comment 3 Beniamino Galvani 2022-02-08 19:53:19 UTC 
In 1.32.2 we did this:

 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/3c55db886a6062010450fd67645815e567b03bbf

so that non-link-local non-deprecated IPv6 addresses are preferred for hostname lookup via DNS.

However, I see in the trace log from https://bugzilla.redhat.com/show_bug.cgi?id=2050296#c5 that you are using NM 1.30 which doesn't have this commit.

Would it be possible for you to try a more recent version of NM?
Comment 4 Yoav Porag 2022-02-16 08:37:29 UTC 
updating the RHCOS image directly as was done in the past is much more problematic with the presence of metal day-1 features.
we've tried to update the NetworkManager post-deployment, however, since nodes are already bugged at this point, the node cant recovered from the necessary reboot.
Comment 11 Ben Nemec 2022-02-23 17:58:35 UTC 
(In reply to Beniamino Galvani from comment #3)
> In 1.32.2 we did this:
> 
>  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/
> 3c55db886a6062010450fd67645815e567b03bbf
> 
> so that non-link-local non-deprecated IPv6 addresses are preferred for
> hostname lookup via DNS.
> 
> However, I see in the trace log from
> https://bugzilla.redhat.com/show_bug.cgi?id=2050296#c5 that you are using NM
> 1.30 which doesn't have this commit.
> 
> Would it be possible for you to try a more recent version of NM?

Okay, this is probably a dupe of 1820770 then. I'm going to mark it that way since we still have the original bug to track the fix in the OCP product. Sorry for the noise, I mistakenly assumed we had that fix in our images already.

*** This bug has been marked as a duplicate of bug 1820770 ***
Comment 15 Red Hat Bugzilla 2023-09-15 01:19:26 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days