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.

Description of problem:
now we have only
   tc setting
       Linux Traffic Control Settings.

┌─────────┬──────────────────┬───────────────┬───────────────────────────────────┐
│Key Name │ Value Type       │ Default Value │ Value Description                 │
├─────────┼──────────────────┼───────────────┼───────────────────────────────────┤
│qdiscs   │ array of vardict │               │ Array of TC queueing disciplines. │
├─────────┼──────────────────┼───────────────┼───────────────────────────────────┤
│tfilters │ array of vardict │               │ Array of TC traffic filters.      │
└─────────┴──────────────────┴───────────────┴───────────────────────────────────┘

this seems a bit incomplete

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

Steps to Reproduce:
1. man nm-settings

*** Bug 1546803 has been marked as a duplicate of this bug. ***

since we are currently using the https://developer.gnome.org/NetworkManager/stable/manpages.html for NM documentation, which manual pages should I add the related documentation ? nm-settings-dbus, or nm-settings-nmcli, or nm-settings-ifcfg-rh ?

(In reply to Wen Liang from comment #3)
> since we are currently using the
> https://developer.gnome.org/NetworkManager/stable/manpages.html for NM
> documentation, which manual pages should I add the related documentation ?
> nm-settings-dbus, or nm-settings-nmcli, or nm-settings-ifcfg-rh ?

all of them. These manual pages describe different aspects of the setting, and the setting is present in all three forms.

That is, you can configure TC settings via nmcli, dbus, ifcfg-rh and keyfile. And -- due to their nature -- the way how this is expressed in detail is not the same and requires (slightly different) documentation.

Upstream PR for fixing it, 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/774

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 (Moderate: NetworkManager security, bug fix, and enhancement 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-2021:4361