Keepalived v2.0.11 sometimes route to VIP isn't being deleted
Yossi Boaron <[email protected]> Tue, 14 May 2019 14:56:10 +0300
| Newsgroups | gmane.linux.keepalived.devel |
|---|---|
| Message-ID | <CAKdxVkTNfZwhbNxj+1yRZUyomRG6B-9xruxa=KTYSVCYvcqawg@mail.gmail.com> |
--===============4322853741643741938==
Content-Type: multipart/alternative; boundary="000000000000b0ec6e0588d7b831"
--000000000000b0ec6e0588d7b831
Content-Type: text/plain; charset="UTF-8"
Hi all,
Sometimes after keepalived set & move a VIP in the system the route for the
VIP IP isn't being deleted.
The VIP (192.168.111.5) should be set to 'eth1' by keepalived as secondary
IP address.
This is the relevant part of both 'ip a' and 'ip route' before keepalived
starts to run:
$ip a:
-----
eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
group default qlen 1000
inet 192.168.111.21/24 brd 192.168.111.255 scope global dynamic
noprefixroute eth1
valid_lft 2889sec preferred_lft 2889sec
$ ip r
default via 192.168.111.1 dev eth1 proto dhcp metric 101
10.128.0.0/14 dev tun0 scope link
172.22.0.0/24 dev eth0 proto kernel scope link src 172.22.0.75 metric 100
172.30.0.0/16 dev tun0
192.168.111.0/24 dev eth1 proto kernel scope link src 192.168.111.21 metric
101
The Keepalived.conf file :
-----------------------------------
vrrp_instance ostest_API {
state BACKUP
interface eth1
virtual_router_id 169
priority 40
advert_int 1
authentication {
auth_type PASS
auth_pass ostest_api_vip
}
virtual_ipaddress {
192.168.123.5
}
track_script {
some_chk_script
}
}
Sometimes after keepalived set&move the VIP (192.168.111.5) from this node,
I can still see the route to the VIP.
ip r:
-----
$ ip r
default via 192.168.111.1 dev eth1 proto dhcp metric 101 10.128.0.0/14
dev tun0 scope link 172.22.0.0/24 dev eth0 proto kernel scope link src
172.22.0.75 metric 100 172.30.0.0/16 dev tun0 192.168.111.0/24 dev
eth1 proto kernel scope link src 192.168.111.21 metric 101
*192.168.111.5 dev eth1 proto kernel scope link src 192.168.111.5
metric 101*
$
OS details
$ uname -mrs
Linux 4.18.0-80.el8.x86_64 x86_64
$
As a result of that, it's impossible to to communicate with the VIP from
this node (e.g: ping 192.168.111.5) I'm getting 'connect: Invalid argument'
error (due to 'src 192.168.111.5').
I tried to search for similar bug in keepalived bug list - but no luck, is
it a known issue in V2.0.11?
Thanks in advance
--000000000000b0ec6e0588d7b831
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr">Hi all,</div><div dir=3D"ltr"><br></div><=
div dir=3D"ltr"><div dir=3D"ltr">Sometimes after keepalived set & move =
a VIP in the system the route for the VIP IP isn't being deleted.</div>=
<div>The VIP (192.168.111.5) should be set to 'eth1' by keepalived =
as secondary IP address.</div><div><br></div><div>This is the relevant part=
of both 'ip a' and 'ip route' before keepalived starts to =
run:</div><div>$ip a:</div><div>-----</div><div dir=3D"ltr">eth1: <BROAD=
CAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group defau=
lt qlen 1000</div><div dir=3D"ltr">=C2=A0 =C2=A0 inet=C2=A0<a href=3D"http:=
//192.168.111.21/24" target=3D"_blank">192.168.111.21/24</a>=C2=A0brd 192.1=
68.111.255 scope global dynamic noprefixroute eth1</div><div dir=3D"ltr">=
=C2=A0 =C2=A0 =C2=A0 =C2=A0valid_lft 2889sec preferred_lft 2889sec</div><di=
v dir=3D"ltr"><br></div><div dir=3D"ltr"><div dir=3D"ltr">$ ip r=C2=A0</div=
><div dir=3D"ltr">default via 192.168.111.1 dev eth1 proto dhcp metric 101=
=C2=A0</div><div dir=3D"ltr"><a href=3D"http://10.128.0.0/14" target=3D"_bl=
ank">10.128.0.0/14</a>=C2=A0dev tun0 scope link=C2=A0</div><div dir=3D"ltr"=
><a href=3D"http://172.22.0.0/24" target=3D"_blank">172.22.0.0/24</a>=C2=A0=
dev eth0 proto kernel scope link src 172.22.0.75 metric 100=C2=A0</div><div=
dir=3D"ltr"><a href=3D"http://172.30.0.0/16" target=3D"_blank">172.30.0.0/=
16</a>=C2=A0dev tun0=C2=A0</div><div dir=3D"ltr"><a href=3D"http://192.168.=
111.0/24" target=3D"_blank">192.168.111.0/24</a>=C2=A0dev eth1 proto kernel=
scope link src 192.168.111.21 metric 101=C2=A0</div><div dir=3D"ltr"><br><=
/div><div dir=3D"ltr"><div dir=3D"ltr">The Keepalived.conf file :</div><div=
dir=3D"ltr">-----------------------------------</div><div dir=3D"ltr">vrrp=
_instance ostest_API {</div><div dir=3D"ltr">=C2=A0 =C2=A0 state BACKUP</di=
v><div dir=3D"ltr">=C2=A0 =C2=A0 interface eth1</div><div dir=3D"ltr">=C2=
=A0 =C2=A0 virtual_router_id 169</div><div dir=3D"ltr">=C2=A0 =C2=A0 priori=
ty 40</div><div dir=3D"ltr">=C2=A0 =C2=A0 advert_int 1</div><div dir=3D"ltr=
">=C2=A0 =C2=A0 authentication {</div><div dir=3D"ltr">=C2=A0 =C2=A0 =C2=A0=
=C2=A0 auth_type PASS</div><div dir=3D"ltr">=C2=A0 =C2=A0 =C2=A0 =C2=A0 au=
th_pass ostest_api_vip</div><div dir=3D"ltr">=C2=A0 =C2=A0 }</div><div dir=
=3D"ltr">=C2=A0 =C2=A0 virtual_ipaddress {</div><div dir=3D"ltr">=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 192.168.123.5</div><div dir=3D"ltr">=C2=A0 =C2=A0 }</div>=
<div dir=3D"ltr">=C2=A0 =C2=A0 track_script {</div><div dir=3D"ltr">=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 some_chk_script</div><div dir=3D"ltr">=C2=A0 =C2=A0 }<=
/div><div dir=3D"ltr">}</div><div dir=3D"ltr"><br></div><br class=3D"gmail-=
m_627745697021074346gmail-Apple-interchange-newline"></div><div>Sometimes a=
fter keepalived set&move the VIP (192.168.111.5) from this node, I can =
still see the route to the VIP.</div><div>ip r:</div><div>-----</div><div><=
pre class=3D"gmail-m_627745697021074346gmail-bz_comment_text" id=3D"gmail-m=
_627745697021074346gmail-comment_text_2" style=3D"white-space:pre-wrap;marg=
in:1em;padding-bottom:1em;width:50em"><font color=3D"#000000">$ ip r=20
default via 192.168.111.1 dev eth1 proto dhcp metric 101=20
<a href=3D"http://10.128.0.0/14" target=3D"_blank">10.128.0.0/14</a> dev tu=
n0 scope link=20
<a href=3D"http://172.22.0.0/24" target=3D"_blank">172.22.0.0/24</a> dev et=
h0 proto kernel scope link src 172.22.0.75 metric 100=20
<a href=3D"http://172.30.0.0/16" target=3D"_blank">172.30.0.0/16</a> dev tu=
n0=20
<a href=3D"http://192.168.111.0/24" target=3D"_blank">192.168.111.0/24</a> =
dev eth1 proto kernel scope link src 192.168.111.21 metric 101=20
</font><b><font color=3D"#ff0000">192.168.111.5 dev eth1 proto kernel scope=
link src 192.168.111.5 metric 101</font></b><font color=3D"#000000">=20
$ </font></pre></div><div><pre class=3D"gmail-bz_comment_text" id=3D"gmail-=
comment_text_0" style=3D"white-space:pre-wrap;margin:1em;padding-bottom:1em=
;width:50em;color:rgb(0,0,0)">OS details</pre><pre class=3D"gmail-bz_commen=
t_text" id=3D"gmail-comment_text_0" style=3D"white-space:pre-wrap;margin:1e=
m;padding-bottom:1em;width:50em;color:rgb(0,0,0)">$ uname -mrs
Linux 4.18.0-80.el8.x86_64 x86_64
$</pre></div><div>As a result of that, it's impossible to to communicat=
e with the VIP from this node (e.g: ping 192.168.111.5) I'm getting =
9;connect: Invalid argument' error (due to 'src 192.168.111.5')=
.</div><div><br></div><div><br></div><div><br></div><div>I tried to search =
for similar bug in keepalived bug list - but no luck, is it a known issue i=
n V2.0.11?</div><div><br></div><div><font color=3D"#333333" face=3D"Roboto,=
PingFang SC, Open Sans, Helvetica Neue, Helvetica, Arial, sans-serif">Than=
ks in advance</font></div></div></div></div>
--000000000000b0ec6e0588d7b831--
--===============4322853741643741938==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--===============4322853741643741938==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Keepalived-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/keepalived-devel
--===============4322853741643741938==--