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.
Hi Michael,
Creation both for mode 5 and mode 6 works well in my RHEL 8.2(NetworkManager-1.22.8-3.el8 and nmstate-0.2.6-2.7.el8).
From the output you provide, it seems you are editing existing bond instead of creating now.
Could test again and provide me the whole output?
Thank you.
(In reply to Gris Ge from comment #1)
> Hi Michael,
>
> Creation both for mode 5 and mode 6 works well in my RHEL
> 8.2(NetworkManager-1.22.8-3.el8 and nmstate-0.2.6-2.7.el8).
>
> From the output you provide, it seems you are editing existing bond instead
> of creating now.
>
> Could test again and provide me the whole output?
>
> Thank you.
HI Gris
pls contact me. this is 100 reproduced on all my machines. I'm not trying to edit exist bond, I'm trying to create new.
Removed the regression flag as it's not a regression issue.
The workaround is marking the slave interface as `absent` when deleting the bond.
RHV team agreed to move this fix to RHEL 8.2.1
(In reply to Gris Ge from comment #4)
> Removed the regression flag as it's not a regression issue.
>
> The workaround is marking the slave interface as `absent` when deleting the
> bond.
Isn't this the intended behavior/workflow, see:
https://github.com/nmstate/nmstate/pull/796> RHV team agreed to move this fix to RHEL 8.2.1
The patch fixing bug #1809330 will also got this covered.
Both bug are impacted by the same root cause.
Closing as duplicate.
*** This bug has been marked as a duplicate of bug 1809330 ***
Description of problem: nmstate can't create bond modes 5 and 6 There is a new regression and nmstate can't create the desired connections for bond modes 5 and 6 any more. MainProcess|jsonrpc/2::INFO::2020-03-08 05:24:43,235::configurator::192::root::(_setup_nmstate) Desired state: {'interfaces': [{'name': 'bond0', 'type': 'bond', 'state': ' up', 'link-aggregation': {'slaves': ['ens4f2', 'ens4f3'], 'options': {'miimon': '100'}, 'mode': 'balance-tlb'}, 'ipv4': {'enabled': False}, 'ipv6': {'enabled': False}}, {' name': 'ovirtmgmt'}]} desired ======= --- name: bond0 type: bond state: up ipv4: enabled: false ipv6: enabled: false link-aggregation: mode: balance-tlb options: active_slave: ens4f2 ad_actor_sys_prio: '' ad_user_port_key: '' miimon: 100 slaves: - ens4f2 - ens4f3 current ======= --- name: bond0 type: bond state: up ipv4: enabled: false ipv6: enabled: false link-aggregation: mode: balance-tlb options: active_slave: ens4f2 ad_actor_sys_prio: '' ad_user_port_key: '' miimon: 100 slaves: - ens4f2 difference ========== --- desired +++ current @@ -15,6 +15,5 @@ miimon: 100 slaves: - ens4f2 - - ens4f3 MainProcess|jsonrpc/7::INFO::2020-03-08 05:33:10,137::configurator::192::root::(_setup_nmstate) Desired state: {'interfaces': [{'name': 'bond0', 'type': 'bond', 'state': ' up', 'link-aggregation': {'slaves': ['ens4f2', 'ens4f3'], 'options': {'miimon': '100'}, 'mode': 'balance-alb'}, 'ipv4': {'enabled': False}, 'ipv6': {'enabled': False}}, {' name': 'ovirtmgmt'}]} desired ======= --- name: bond0 type: bond state: up ipv4: enabled: false ipv6: enabled: false link-aggregation: mode: balance-alb options: active_slave: ens4f2 ad_actor_sys_prio: '' ad_user_port_key: '' miimon: 100 slaves: - ens4f2 - ens4f3 current ======= --- name: bond0 type: bond state: up ipv4: enabled: false ipv6: enabled: false link-aggregation: mode: balance-alb options: active_slave: ens4f2 ad_actor_sys_prio: '' ad_user_port_key: '' miimon: 100 slaves: - ens4f2 difference ========== --- desired +++ current @@ -15,6 +15,5 @@ miimon: 100 slaves: - ens4f2 - - ens4f3 Version-Release number of selected component (if applicable): nmstate-0.2.6-1.el8.noarch NetworkManager-1.22.8-3.el8.x86_64 vdsm-4.40.5-1.el8ev.x86_64 How reproducible: 100% Steps to Reproduce: 1. Try to create bond mode 5 or 6 using nmstate Actual results: nmstate failed to create the desired connection Expected results: Must work as expected Additional info: Blocks the work around for the next bugs: BZ 1809330 BZ 1810550 NOte that creations of bond modes 5 and 6 wroked in previous nmstate versions.