Bug 1983105

Summary: nft: man: hide features not supported by the kernel
Product: Red Hat Enterprise Linux 8 Reporter: Eric Garver <egarver>
Component: nftablesAssignee: Phil Sutter <psutter>
Status: CLOSED WONTFIX QA Contact: Jiri Peska <jpeska>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.5CC: jpeska, todoleza
Target Milestone: betaKeywords: FutureFeature, ManPageChange, Reopened, Triaged
Target Release: 8.8   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-17 07:28:13 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: 1983108    
Bug Blocks:    

Description Eric Garver 2021-07-16 14:17:01 UTC
nft userspace often gets rebased and thus includes documentation for features that may not be enabled in the kernel. We should identify these and hide them from the man pages.

When the kernel support is added then we can revive the hidden man page sections.

Comment 9 Phil Sutter 2022-08-31 17:22:00 UTC
Missed RHEL8.7, proposing for RHEL8.8. Resetting qa_ack+ and thereby requesting
explicit commitment for ITM-5.

Adding an artificial dependency upon Bug 1983108 - I may carry the man page
adjustments out "blindly" but doing it based on testsuite results adds
confidence and ensures correctness in case of future changes.

Comment 11 RHEL Program Management 2023-01-16 07:27:37 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 14 RHEL Program Management 2023-07-17 07:28:13 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.