Bug 2211623

Summary: resolv.conf man page needs update for no-aaaa from 2096189
Product: [Fedora] Fedora Reporter: Petr Menšík <pemensik>
Component: man-pagesAssignee: Nikola Forró <nforro>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 39CC: dstehlik, fweimer, jchaloup, kasal, ljavorsk, mpoole, nforro, osloup, qguo
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2184023 Environment:
Last Closed: 2024-11-27 21:12:33 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: 2184023    
Bug Blocks:    

Description Petr Menšík 2023-06-01 09:00:19 UTC
+++ This bug was initially created as a clone of Bug #2184023 +++

Description of problem:

BZ2096189 introduced a new no-aaaa option for resolv.conf which is not covered in the current overrides man page.


Version-Release number of selected component (if applicable):

  man-pages-overrides-8.6.0.0-1.el8

Additional info:

This probably need duplicating into RHEL9 as well.

--- Additional comment from Lukas Javorsky on 2023-04-12 18:59:23 CEST ---

Proposed to upstream with some improvements after their review: https://marc.info/?l=linux-man&m=168131276816867&w=2

This is not documented even in rawhide, where that no-aaaa option is already implemented. But not documented.

Comment 1 Petr Menšík 2023-06-01 09:08:11 UTC
I have created bug #2182745, because I had no idea this is already partially implemented. Therefore it is there since Fedora 37

This should be implemented since glibc 2.36, according to:
https://sourceware.org/pipermail/libc-alpha/2022-August/141193.html

Comment 2 Lukas Javorsky 2023-06-02 10:33:46 UTC
This is already part of the RHEL-9 via: https://issues.redhat.com/browse/RHEL-454

Comment 3 Nikola Forró 2023-06-06 07:30:51 UTC
I assume it will be part of the next upstream release:
https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=391bf54cfd5daf93fc904959d062259065c94ffc

Comment 4 Fedora Release Engineering 2023-08-16 08:10:01 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 5 Aoife Moloney 2024-11-08 10:53:00 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Aoife Moloney 2024-11-27 21:12:33 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.