Bug 1983105 - nft: man: hide features not supported by the kernel
Summary: nft: man: hide features not supported by the kernel
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nftables
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: beta
: 8.8
Assignee: Phil Sutter
QA Contact: Jiri Peska
URL:
Whiteboard:
Depends On: 1983108
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-16 14:17 UTC by Eric Garver
Modified: 2023-07-17 07:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-17 07:28:13 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1983108 1 unspecified CLOSED nft: tests: mark tests for features not in kernel as expected failures 2023-07-17 07:29:46 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.