On Mon, Aug 22, 2016 at 02:54:46PM +0200, Jan Tluka wrote:

The ip6 address was needed to configure 3 vlans over bond setup. Originally this was a workaround for NM bug. With updated NetworkManager the ip6 address causes that NM gets stuck on bond device configuration and never activates it. The solution is to remove the address as the workaround is no more needed.

Tested with NM: version 1.4

Signed-off-by: Jan Tluka jtluka@redhat.com

recipes/regression_tests/phase1/3_vlans_over_active_backup_bond.xml | 3 --- 1 file changed, 3 deletions(-)

diff --git a/recipes/regression_tests/phase1/3_vlans_over_active_backup_bond.xml b/recipes/regression_tests/phase1/3_vlans_over_active_backup_bond.xml index f9b4922..26300b1 100644 --- a/recipes/regression_tests/phase1/3_vlans_over_active_backup_bond.xml +++ b/recipes/regression_tests/phase1/3_vlans_over_active_backup_bond.xml @@ -32,9 +32,6 @@ <slave id="eth1" /> <slave id="eth2" /> </slaves>

•                <addresses>
  

•                    <address value="2002::1/64" />
  

•                </addresses>
             </bond>
             <vlan id="vlan10">
                 <options>
  

-- 2.4.11 _______________________________________________ LNST-developers mailing list lnst-developers@lists.fedorahosted.org https://lists.fedorahosted.org/admin/lists/lnst-developers@lists.fedorahoste...

thanks, pushing to master

-Ondrej