-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
None
-
None
-
None
-
rhel-sst-virtualization
-
ssg_virtualization
-
None
-
QE ack
-
False
-
-
None
-
None
-
None
-
None
-
None
What were you trying to do that didn't work?
The live xml and libvirt.org shows bridge forward-delay is 0, but in fact it's 2 seconds
Please provide the package NVR for which bug is seen:
libvirt-9.5.0-7.el9_3.x86_64
How reproducible:
100%
Steps to reproduce:
1. The libvirt.org shows:
"Attribute stp specifies if Spanning Tree Protocol is 'on' or 'off' (default is 'on'). Attribute delay sets the bridge's forward delay value in seconds (default is 0)"
2. The default network xml shows it's delay is 0
# virsh net-dumpxml default | grep bridge <bridge name='virbr0' stp='on' delay='0'/> # virsh net-start default Network default started # virsh net-dumpxml default | grep bridge <bridge name='virbr0' stp='on' delay='0'/>
3. But the system file shows the delay is 2 seconds:
# cat /sys/class/net/virbr0/bridge/forward_delay
200
# nmcli con show virbr0 | grep forward-delay
bridge.forward-delay: 2
Expected results
The live xml and libvirt.org should be consistent with the actual value
Actual results
The live xml and libvirt.org are not consistent with the actual situation, which is a little confusing