CTDB failover with multiple VLAN tagged bonded interfaces don't work

[Robin Jonsson]

Wow, thanks! Works perfectly!

I filed a bugzilla for this also (#1080958).

Just to be sure, is this a non existing issue in the more recent releases of CTDB? :)

Thanks again!

Regards,
Robin

On 26 Mar 2014, at 9:32 am, Martin Schwenke <martin at meltin.net> wrote:

> On Wed, 26 Mar 2014 08:09:24 +0000, Robin Jonsson
> <Robin.Jonsson at enfo.se> wrote:
> 
>> Thanks for getting back to me!
>> 
>> Here's the requested output:
>> 
>> Public IPs on node 0
>> 192.168.4.4 node[0] active[bond0.123] available[bond0.123] configured[bond0.123]
>> 192.168.4.72 node[-1] active[] available[] configured[bond0.124]
>> 
>> Public IPs on node 1
>> 192.168.4.4 node[0] active[] available[bond0.123] configured[bond0.123]
>> 192.168.4.72 node[-1] active[] available[] configured[bond0.124]
>> 
>> Interfaces on node 0
>> name:bond0.124 link:down references:0
>> name:bond0.123 link:up references:1
>> 
>> Interfaces on node 1
>> name:bond0.124 link:down references:0
>> name:bond0.123 link:up references:0
>> 
>> I raised the debug level to INFO and went through 'log.ctdb'. I still wasn't able to find anything obviously wrong. Only the first VIP gets assigned and it doesn't matter what order i specify the interfaces in public_addresses. Only the lowest one(bond0.123) gets assigned. If I remove bond0.123 and only use bond0.124, I can successfully online and use this VIP aswell...
> 
> This is wrong:
> 
>               test -n "$OLDLINK" && {
>                        ok=1 # we only set ok for interfaces known to ctdbd
>                        ctdb setifacelink $IFACE up
>                }
>                return 0;
>            }
> 
> The script returns after processing the 1st bond.  Please try changing
> the "return 0" to "continue".
> 
> 10.interface in more recent versions of CTDB is much neater...  :-)
> 
> peace & happiness,
> martin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20140326/243a0c4d/attachment-0001.pgp>