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.
This is related to the `fail_over_mac: "1"` option.
Even without VLAN, apply the same yml file again will cause the same failure.
Upstream tracking issue is: https://github.com/nmstate/nmstate/issues/781
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-2020:1696
Description of problem: VLAN cannot be added to existing bond interface configured in a custom Mode 1 if the option "fail_over_mac=active" is set - For vlan bridge: MainProcess|jsonrpc/5::INFO::2020-02-11 11:07:39,466::configurator::192::root::(_setup_nmstate) Desired state: {'interfaces': [{'name': 'bond0', 'type': 'bond', 'state': ' up', 'link-aggregation': {'slaves': ['ens4f2', 'ens4f3'], 'options': {'fail_over_mac': '1', 'miimon': '100'}, 'mode': 'active-backup'}, 'mtu': 1500}, {'vlan': {'id': 335, 'base-iface': 'bond0'}, 'name': 'bond0.335', 'type': 'vlan', 'state': 'up', 'mtu': 1500, 'ipv4': {'enabled': False}, 'ipv6': {'enabled': False}}, {'name': 'ovirtmgmt'}, {' name': 'vlan1', 'type': 'linux-bridge', 'state': 'up', 'mtu': 1500, 'bridge': {'port': [{'name': 'bond0.335'}], 'options': {'stp': {'enabled': False}}}, 'ipv4': {'enabled' : False}, 'ipv6': {'enabled': False}}]} MainProcess|jsonrpc/5::DEBUG::2020-02-11 11:07:39,683::connection::217::root::(_active_connection_callback) Connection activation initiated: dev=bond0, con-state=<enum NM_ACTIVE_CONNECTION_STATE_ACTIVATING of type NM.ActiveConnectionState> MainProcess|jsonrpc/5::ERROR::2020-02-11 11:07:40,301::nmclient::178::root::(quit) NM main-loop aborted: Connection activation failed on bond0: reason=<enum NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED of type NM.ActiveConnectionStateReason> libnmstate.error.NmstateLibnmError: Unexpected failure of libnm when running the mainloop: run execution - For vlan MainProcess|jsonrpc/5::INFO::2020-02-11 11:14:44,659::configurator::192::root::(_setup_nmstate) Desired state: {'interfaces': [{'name': 'bond0', 'type': 'bond', 'state': ' up', 'link-aggregation': {'slaves': ['ens4f2', 'ens4f3'], 'options': {'fail_over_mac': '1', 'miimon': '100'}, 'mode': 'active-backup'}, 'mtu': 1500}, {'vlan': {'id': 162, 'base-iface': 'bond0'}, 'name': 'bond0.162', 'type': 'vlan', 'state': 'up', 'mtu': 1500, 'ipv4': {'enabled': False}, 'ipv6': {'enabled': False}}, {'name': 'ovirtmgmt'}]} Version-Release number of selected component (if applicable): nmstate-0.2.1-1.el8.noarch How reproducible: 100% Steps to Reproduce: 1. Create a custom bond mode 1 interface with custom option fail_over_mac=active 2. Try to attach vlan bridge or vlan network on top of it Actual results: nmstate explodes and fail to create desired connection Expected results: Should work