(In reply to Jianlin Shi from comment #0)
> Description of problem:
> WARN|bad ipv6 address in ovn-northd.log when add on-link ipv6 route
> 
> Version-Release number of selected component (if applicable):
> ovn-2021-21.06.0-29.el8
> 
> How reproducible:
> Always
> 
> Steps to Reproduce:
> systemctl start openvswitch          
> systemctl start ovn-northd                           
> ovn-nbctl set-connection ptcp:6641
> ovn-sbctl set-connection ptcp:6642                           
> ovs-vsctl set open . external_ids:system-id=hv1
> external_ids:ovn-remote=tcp:1.1.40.25:6642
> external_ids:ovn-encap-type=geneve external_ids:ovn-encap-ip=1.1.40.25
> systemctl restart ovn-controller                        
>                                                         
> ovn-nbctl ls-add ls1
> ovn-nbctl lsp-add ls1 ls1p1
> ovn-nbctl lsp-set-addresses ls1p1 "00:00:00:01:01:01 192.168.1.1 2001::1"
> ovn-nbctl lsp-add ls1 ls1p2
> ovn-nbctl lsp-set-addresses ls1p2 "00:00:00:01:01:02 192.168.1.2 2001::2"
> 
> ovn-nbctl lr-add lr1                                                        
> 
> ovn-nbctl lrp-add lr1 lr1-ls1 00:00:00:00:00:01 192.168.1.254/32 2001::a/128
> 
> ovn-nbctl lsp-add ls1 ls1-lr1
> ovn-nbctl lsp-set-addresses ls1-lr1 "00:00:00:00:00:01 192.168.1.254 2001::a"
> ovn-nbctl lsp-set-type ls1-lr1 router
> ovn-nbctl lsp-set-options ls1-lr1 router-port=lr1-ls1          
>                                         
> ovn-nbctl --may-exist lr-route-add lr1 192.168.1.0/24 lr1-ls1
> ovn-nbctl --may-exist lr-route-add lr1 192.168.1.0/24 lr1-ls1
> ovn-nbctl --may-exist lr-route-add lr1 2001::/64 lr1-ls1            
> ovn-nbctl --may-exist lr-route-add lr1 2001::/64 lr1-ls1         
> 
> ovn-nbctl lrp-add lr1 lr1-ls2 00:00:00:00:00:02 192.168.2.254/32 2002::a/128
>                               
> ovn-nbctl ls-add ls2                                           
> ovn-nbctl lsp-add ls2 ls2-lr1           
> ovn-nbctl lsp-set-addresses ls2-lr1 "00:00:00:00:00:02 192.168.2.254 2002::a"
> ovn-nbctl lsp-set-type ls2-lr1 router               
> ovn-nbctl lsp-set-options ls2-lr1 router-port=lr1-ls2               
>                                                                  
> ovn-nbctl --may-exist lr-route-add lr1 192.168.2.0/24 lr1-ls2
> ovn-nbctl --may-exist lr-route-add lr1 192.168.2.0/24 lr1-ls2
> ovn-nbctl --may-exist lr-route-add lr1 2002::/64 lr1-ls2
> ovn-nbctl --may-exist lr-route-add lr1 2002::/64 lr1-ls2
>                                       
> ovn-nbctl lsp-add ls2 ls2p1       
> ovn-nbctl lsp-set-addresses ls2p1 "00:00:00:01:02:01 192.168.2.1 2002::1"
> ovn-nbctl lsp-add ls2 ls2p2 
> ovn-nbctl lsp-set-addresses ls2p2 "00:00:00:01:02:02 192.168.2.2 2002::2"
> 
> ovs-vsctl add-port br-int ls1p1 -- set interface ls1p1 type=internal
> external_ids:iface-id=ls1p1
> ovs-vsctl add-port br-int ls2p1 -- set interface ls2p1 type=internal
> external_ids:iface-id=ls2p1
> 
> ip netns add ls1p1
> ip link set ls1p1 netns ls1p1
> ip netns exec ls1p1 ip link set ls1p1 address 00:00:00:01:01:01
> ip netns exec ls1p1 ip link set ls1p1 up
> ip netns exec ls1p1 ip addr add 192.168.1.1/24 dev ls1p1
> ip netns exec ls1p1 ip addr add 2001::1/64 dev ls1p1
> ip netns exec ls1p1 ip route add default via 192.168.1.254 dev ls1p1
> ip netns exec ls1p1 ip -6 route add default via 2001::a dev ls1p1
> 
> ip netns add ls2p1 
> ip link set ls2p1 netns ls2p1
> ip netns exec ls2p1 ip link set ls2p1 address 00:00:00:01:02:01
> ip netns exec ls2p1 ip link set ls2p1 up
> ip netns exec ls2p1 ip addr add 192.168.2.1/24 dev ls2p1
> ip netns exec ls2p1 ip addr add 2002::1/64 dev ls2p1
> ip netns exec ls2p1 ip route add default via 192.168.2.254 dev ls2p1
> ip netns exec ls2p1 ip -6 route add default via 2002::a dev ls2p1
> 
> sleep 3
> 
> ip netns exec ls1p1 ping 192.168.2.1 -c 1
> ip netns exec ls1p1 ping6 2002::1 -c 1
> 
> Actual results:
> [root@wsfd-advnetlab16 ~]# grep WARN /var/log/ovn/ovn-northd.log
> 2021-09-18T06:01:37.909Z|00008|ovn_northd|WARN|bad ipv6 address
> 
> Expected results:
> no WARN
> 
> Additional info:
> 
> [root@wsfd-advnetlab16 bz1982551]# rpm -qa | grep -E
> "openvswitch2.15|ovn-2021"
> ovn-2021-21.06.0-29.el8fdp.x86_64
> python3-openvswitch2.15-2.15.0-38.el8fdp.x86_64
> ovn-2021-central-21.06.0-29.el8fdp.x86_64
> openvswitch2.15-2.15.0-38.el8fdp.x86_64
> ovn-2021-host-21.06.0-29.el8fdp.x86_64
> 
> related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1982551#c7

I think this bug is already fixed by:
https://github.com/ovn-org/ovn/commit/ab4bdb55cd04ca38f1823f367f6ffb28a3fd5250

I guess we can close this bz as 'current release'

on which downstream version is the issue fixed?

(In reply to Jianlin Shi from comment #2)
> on which downstream version is the issue fixed?

it is not fixed in any downstream version since I do not think it worths to backport it, this is just a warning not causing any real problem

confirmed that the issue is fixed on ovn22.06-22.06.0-27.el8