Wrong LACP parameter when using Linux native bonding in active/backup

[Laurent Perrin]

We use Fuel Cli to configure two interfaces in active/backup mode with Linux bonding.

But in the bonding interface, a LACP parameter "bond-lacp-rate" is used. The network connection through this bonding interface is not working and causes a deployment failure.

Removing this LACP parameters solves the network issue.

Here is the configuration used with Fuel CLI:
" - action: add-bond
    bridge: br-bond0
    interfaces: [eth0, eth4]
    provider: lnx
    properties:
     mode: 1
    name: bond0
  - action: add-br
    name: br-ex
  - action: add-br
    name: br-mgmt
  - action: add-br
    name: br-storage
  - action: add-br
    name: br-fw-admin
  - action: add-patch
    bridges:
    - br-eth1
    - br-storage
    trunks:
    - 0
  - action: add-patch
    bridges:
    - br-bond0
    - br-mgmt
    tags:
    - 174
    - 0
    vlan_ids:
    - 174
    - 0
  - action: add-patch
    bridges:
    - br-bond0
    - br-fw-admin
    trunks:
    - 0
"

[Laurent Perrin (perrin-laurent)]

After new tests, it seems that the bond-lacp-parameter is not the cause of this issue.

While we deploy an environnement with bonding, the node becomes offline when the network parameters are pushed. We have to restart the openvswitch-switch service and the node come back online.

[Sergii Golovatiuk (sgolovatiuk)]

I have tried to reproduce this bug in Fuel labs. If issue is still present on your environment, please generate diagnostic snapshot. Attach it to this bug so Fuel team will be able to investigate it in details.

[Stanislaw Bogatkin (sbogatkin)]

This bug was incomplete for 6.1 release more than 4 weeks. We cannot investigate it further so we are setting the status to Invalid. If you think it is not correct, please feel free to provide requested information and reopen the bug, and we will look into it further.