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.
Bug 1806452 - Use kernel runtime bridge status instead of on-disk configuration
Summary: Use kernel runtime bridge status instead of on-disk configuration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nmstate
Version: 8.2
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: 8.3
Assignee: Fernando F. Mancera
QA Contact: Mingyu Shi
URL:
Whiteboard:
Depends On:
Blocks: 1817466
TreeView+ depends on / blocked
 
Reported: 2020-02-24 08:58 UTC by Mingyu Shi
Modified: 2020-11-04 03:10 UTC (History)
9 users (show)

Fixed In Version: nmstate-0.3.2-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1817466 (view as bug list)
Environment:
Last Closed: 2020-11-04 03:08:25 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
verified.log (9.93 KB, text/plain)
2020-07-22 03:25 UTC, Mingyu Shi
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github nmstate nmstate pull 883 0 None closed nm.bridge: get ports from sysfs 2020-08-03 06:45:34 UTC
Red Hat Product Errata RHBA-2020:4696 0 None None None 2020-11-04 03:08:48 UTC

Comment 1 Fernando F. Mancera 2020-02-27 13:29:32 UTC
Is this a problem for RHV? Should we target it for 8.2 or 8.2.1?

Comment 2 Dominik Holler 2020-02-27 16:38:59 UTC
I am not aware that this is a problem for RHV. Ales, do we have a workaround in VDSM I am not aware of?

Comment 3 Ales Musil 2020-03-02 06:10:31 UTC
We are using only some parts from nmstate for getting caps and slaves are not one of them. Only flow that might cause some troubles is MTU for bond slaves AFAIK.

Comment 4 Gris Ge 2020-03-13 12:27:35 UTC
Currently, nmstate is incorrectly showing the slaves from on-disk profiles.

Will fix by by showing kernel runtime status when query.

Comment 12 Mingyu Shi 2020-07-22 03:25:50 UTC
Created attachment 1702020 [details]
verified.log

Verified with versions:
nmstate-0.3.3-2.el8.noarch
NetworkManager-1.26.0-2.el8.x86_64
DISTRO=RHEL-8.3.0-20200721.n.0
Linux dell-r330-15.gsslab.brq.redhat.com 4.18.0-226.el8.x86_64 #1 SMP Wed Jul 15 07:40:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Comment 15 errata-xmlrpc 2020-11-04 03:08:25 UTC
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 (nmstate 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/RHBA-2020:4696


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