Hide Forgot
Created attachment 1728245 [details] log Description of problem: If fail_over_mac=active is set in a bond, you cannot change state of any other interface: libnmstate.error.NmstateValueError: MAC address cannot be specified in bond interface along with fail_over_mac active on active backup mode We should ignore its mac when a bond is as fail_over_mac=active Version-Release number of selected component (if applicable): nmstate-0.4.1-2.el8.noarch nispor-0.6.1-2.el8.x86_64 NetworkManager-1.28.0-0.1.el8.x86_64 DISTRO=RHEL-8.4.0-20201103.d.0 Linux rdma05.rhts.eng.pek2.redhat.com 4.18.0-241.el8.dt1.x86_64 #1 SMP Mon Nov 2 08:24:31 EST 2020 x86_64 x86_64 x86_64 GNU/Linux How reproducible: 100% Steps to Reproduce: echo "interfaces: - name: bond1 type: bond state: up link-aggregation: mode: active-backup options: fail_over_mac: active " | nmstatectl set nmstatectl show bond1 echo "interfaces: - name: dummy1 type: dummy state: up" | nmstatectl set Actual results: libnmstate.error.NmstateValueError: MAC address cannot be specified in bond interface along with fail_over_mac active on active backup mode Expected results: Success Additional info: A workaround is to edit bond1's state at the same time, remove 'mac' property of bond1
Hi Mingyu, can you try this again with the latest nmstate? Thank you!
*** Bug 1966734 has been marked as a duplicate of this bug. ***
With `fail_over_mac: active` in `active-backup` mode, you cannot define mac adress in desire state. This is the limitation of kernel and defination of `fail_over_mac`. Nmstate is raise the expected exception NmstateValueError
Verified with versions: nmstate-1.1.0-0.3.alpha3.el8.noarch nispor-1.1.0-2.el8.x86_64 NetworkManager-1.32.0-0.5.el8.x86_64
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-2021:4157