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.

+++ This bug was initially created as a clone of Bug #2117482 +++

Description of problem:

Nmstate currently is ignoring STP settings when STP is disabled. We should raise an warning for state like:

```
      stp:
        enabled: false
        forward-delay: 15
        hello-time: 2
        max-age: 20
        priority: 32768
```

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

Nmstate is silently ignoring STP settings after STP disabled.

Expected results:

An warning message indicate nmstate is ignoring the changes to STP setting when STP disabled.

Additional info:

RHV use case require nmstate to apply the STP setting regardless it is enabled or not. Since kernel allows so and no harm to other user.

Changing the goal of this bug to apply STP settings even disabled.

RHEL 8.6 backport scratch build could be found at https://people.redhat.com/fge/bz_2117485/

Patch sent to upstream: https://github.com/nmstate/nmstate/pull/2036

Even with nmstate allowing setting STP options with disabled STP, NetworkManager `ifcfg-rh` format connection will reject it. The `keyfile` format works well.

Waiting RHV team decision on action plan.

The NetworkManager has explicit check against this use case:


        if (m[i].only_with_stp && !stp) {
            PARSE_WARNING("'%s' invalid when STP is disabled", key);
            return;
        }


Just FYI.

RHV decided not to pursue this use case any more due to limitation in NetworkManager ifcfg.

This use case works well in RHEL 9.1 where NetworkManager is defaulting keyfile storage and nmstate rust is applying STP settings regardless STP status.

Closing as won't fix.