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:
STP is not updated once bringing up a bridge with "STP=on". 

How reproducible:
Always.

Steps to Reproduce:
1. Create an ifcfg-br0 config for a bridge with STP=on (NM_CONTROLLED=no)
2. ifup br0
3. cat /sys/class/net/br0/bridge/stp_state 

Actual results:
0

Expected results:
1

Additional info:
example setup:

ifcfg-dummy:
DEVICE=dummy
BRIDGE=br0
ONBOOT=yes
MTU=1500
DEFROUTE=no
NM_CONTROLLED=no
IPV6INIT=no

ifcfg-br0:
DEVICE=br0
TYPE=Bridge
DELAY=0
STP=on
ONBOOT=yes
MTU=1500
DEFROUTE=no
NM_CONTROLLED=no
IPV6INIT=no

Introduced in this PR https://github.com/fedora-sysv/initscripts/pull/213

Thank you for your PR. Changes are already merged into master branch. 
I also created PR into rhel8-branch based on your commit.

https://github.com/fedora-sysv/initscripts/pull/284

This bug will be fixed in RHEL 8.2.0.

(In reply to Jan Macku from comment #1)
> Thank you for your PR. Changes are already merged into master branch. 
> I also created PR into rhel8-branch based on your commit.
> 
> https://github.com/fedora-sysv/initscripts/pull/284
> 
> This bug will be fixed in RHEL 8.2.0.

Thank you very much, Jan!
RHV likes to have this fix in RHEL 8.1.
Does the bug require some flags or keywords to trigger this?

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, 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/RHBA-2019:3612