Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2093428

Summary: Cannot apply linux bridge with full bridge options
Product: Red Hat Enterprise Linux 9 Reporter: Mingyu Shi <mshi>
Component: nmstateAssignee: Gris Ge <fge>
Status: CLOSED ERRATA QA Contact: Mingyu Shi <mshi>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.1CC: ferferna, jiji, jishi, network-qe, sfaye, till
Target Milestone: rcKeywords: Regression, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nmstate-2.1.2-1.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-15 10:01:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2091421    

Description Mingyu Shi 2022-06-03 16:51:54 UTC 
Description of problem:
Cannot apply linux bridge with full bridge options.
This works well on RHEL 8.

Version-Release number of selected component (if applicable):
2.1.1-0.alpha.20220602.5accbd1.el9

How reproducible:
100%

Steps to Reproduce:
echo "
interfaces:
- name: br0
  type: linux-bridge
  state: up
  bridge:
    port:
    - name: dummy0
- name: dummy0
  state: up
  type: dummy
" | nmstatectl apply

echo "
interfaces:
- name: br0
  type: linux-bridge
  state: up
  bridge:
    options:
      gc-timer: 0
      group-addr: 01:80:C2:00:00:04
      group-forward-mask: 16384
      hash-max: 1
      hello-timer: 0
      mac-ageing-time: 1
      multicast-last-member-count: 0
      multicast-last-member-interval: 0
      multicast-querier: true
      multicast-querier-interval: 0
      multicast-query-interval: 0
      multicast-query-response-interval: 0
      multicast-query-use-ifaddr: true
      multicast-router: 0
      multicast-snooping: true
      multicast-startup-query-count: 0
      multicast-startup-query-interval: 0
" | nmstatectl apply

Actual results:
[2022-06-03T15:03:53Z INFO  nmstate::nispor::show] Got unsupported interface lo type Loopback
[2022-06-03T15:03:53Z INFO  nmstate::nm::show] Got unsupported interface type generic: lo, ignoring
[2022-06-03T15:03:53Z INFO  nmstate::net_state] Ignoring kernel interface eno2
[2022-06-03T15:03:53Z INFO  nmstate::net_state] Ignoring kernel interface eno3
[2022-06-03T15:03:53Z INFO  nmstate::net_state] Ignoring kernel interface lo
[2022-06-03T15:03:53Z INFO  nmstate::net_state] Ignoring kernel interface eno4
[2022-06-03T15:03:53Z INFO  nmstate::ifaces::inter_ifaces] Changing interface br0 with type linux-bridge
[2022-06-03T15:03:53Z INFO  nmstate::net_state] Created checkpoint /org/freedesktop/NetworkManager/Checkpoint/2
[2022-06-03T15:03:53Z INFO  nmstate::nm::profile] Creating/Modifying connection UUID Some("b9ed4181-1494-4185-9822-29eaeb73e4e4"), ID Some("br0"), type Some("bridge") name Some("br0")
[2022-06-03T15:03:53Z INFO  nmstate::nm::profile] Activating connection b9ed4181-1494-4185-9822-29eaeb73e4e4: br0/bridge
[2022-06-03T15:03:53Z INFO  nmstate::nm::profile] Reapply operation failed trying activation, reason: Can't reapply any changes to 'bridge' setting, retry on normal activation
[2022-06-03T15:03:53Z INFO  nmstate::nispor::show] Got unsupported interface lo type Loopback
[2022-06-03T15:03:53Z INFO  nmstate::nm::show] Got unsupported interface type generic: lo, ignoring
[2022-06-03T15:03:53Z INFO  nmstate::net_state] Retrying on verification failure: VerificationError: Verification failure: br0.interface.bridge.options.group-addr desire '"01:80:C2:00:00:04"', current '"01:80:C2:00:00:00"'
[2022-06-03T15:03:54Z INFO  nmstate::nispor::show] Got unsupported interface lo type Loopback
[2022-06-03T15:03:54Z INFO  nmstate::nm::show] Got unsupported interface type generic: lo, ignoring
[2022-06-03T15:03:54Z INFO  nmstate::net_state] Retrying on verification failure: VerificationError: Verification failure: br0.interface.bridge desire '{"options":{"group-addr":"01:80:C2:00:00:04","group-forward-mask":16384,"hash-max":1,"mac-ageing-time":1,"multicast-last-member-count":0,"multicast-last-member-interval":0,"multicast-querier":true,"multicast-querier-interval":0,"multicast-query-interval":0,"multicast-query-response-interval":0,"multicast-query-use-ifaddr":true,"multicast-router":"disabled","multicast-snooping":true,"multicast-startup-query-count":0,"multicast-startup-query-interval":0}}', current 'null'
[2022-06-03T15:03:55Z INFO  nmstate::nispor::show] Got unsupported interface lo type Loopback
[2022-06-03T15:03:55Z INFO  nmstate::nm::show] Got unsupported interface type generic: lo, ignoring
[2022-06-03T15:03:55Z INFO  nmstate::net_state] Retrying on verification failure: VerificationError: Verification failure: br0.interface.bridge desire '{"options":{"group-addr":"01:80:C2:00:00:04","group-forward-mask":16384,"hash-max":1,"mac-ageing-time":1,"multicast-last-member-count":0,"multicast-last-member-interval":0,"multicast-querier":true,"multicast-querier-interval":0,"multicast-query-interval":0,"multicast-query-response-interval":0,"multicast-query-use-ifaddr":true,"multicast-router":"disabled","multicast-snooping":true,"multicast-startup-query-count":0,"multicast-startup-query-interval":0}}', current 'null'
[2022-06-03T15:03:56Z INFO  nmstate::nispor::show] Got unsupported interface lo type Loopback
[2022-06-03T15:03:56Z INFO  nmstate::nm::show] Got unsupported interface type generic: lo, ignoring
[2022-06-03T15:03:56Z INFO  nmstate::net_state] Retrying on verification failure: VerificationError: Verification failure: br0.interface.bridge desire '{"options":{"group-addr":"01:80:C2:00:00:04","group-forward-mask":16384,"hash-max":1,"mac-ageing-time":1,"multicast-last-member-count":0,"multicast-last-member-interval":0,"multicast-querier":true,"multicast-querier-interval":0,"multicast-query-interval":0,"multicast-query-response-interval":0,"multicast-query-use-ifaddr":true,"multicast-router":"disabled","multicast-snooping":true,"multicast-startup-query-count":0,"multicast-startup-query-interval":0}}', current 'null'
[2022-06-03T15:03:57Z INFO  nmstate::nispor::show] Got unsupported interface lo type Loopback
[2022-06-03T15:03:57Z INFO  nmstate::nm::show] Got unsupported interface type generic: lo, ignoring
[2022-06-03T15:03:58Z INFO  nmstate::net_state] Rollbacked to checkpoint /org/freedesktop/NetworkManager/Checkpoint/2
NmstateError: VerificationError: Verification failure: br0.interface.bridge desire '{"options":{"group-addr":"01:80:C2:00:00:04","group-forward-mask":16384,"hash-max":1,"mac-ageing-time":1,"multicast-last-member-count":0,"multicast-last-member-interval":0,"multicast-querier":true,"multicast-querier-interval":0,"multicast-query-interval":0,"multicast-query-response-interval":0,"multicast-query-use-ifaddr":true,"multicast-router":"disabled","multicast-snooping":true,"multicast-startup-query-count":0,"multicast-startup-query-interval":0}}', current 'null'

Expected results:
No failure

Additional info:
Comment 1 Gris Ge 2022-07-06 05:43:25 UTC 
The kernel code `br_multicast_set_query_intvl()` and `br_multicast_set_startup_query_intvl` have limited the minimum value for multicast-startup-query-interval and multicast-query-interval are 100.

These kernel logs are also confirming this. 

[529659.272296] br0: trying to set multicast query interval below minimum, setting to 100 (1000ms)
[529659.272299] br0: trying to set multicast startup query interval below minimum, setting to 100 (1000ms)


Once changing those value to 100, nmstate-2.1.2-1.el9 works well.
Comment 4 Mingyu Shi 2022-08-04 08:55:51 UTC 
(In reply to Gris Ge from comment #1)
> The kernel code `br_multicast_set_query_intvl()` and
> `br_multicast_set_startup_query_intvl` have limited the minimum value for
> multicast-startup-query-interval and multicast-query-interval are 100.
> 
> These kernel logs are also confirming this. 
> 
> [529659.272296] br0: trying to set multicast query interval below minimum,
> setting to 100 (1000ms)
> [529659.272299] br0: trying to set multicast startup query interval below
> minimum, setting to 100 (1000ms)
> 
> 
> Once changing those value to 100, nmstate-2.1.2-1.el9 works well.

Thanks for clarification.
Verified with:
nmstate-2.1.3-1.el9.x86_64
NetworkManager-1.39.10-1.el9.x86_64
Comment 6 errata-xmlrpc 2022-11-15 10:01:03 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-2022:7991