On Fri, Jul 9, 2021 at 9:26 AM Lionel Caignec <caig...@cines.fr> wrote:
> Hi, > > i've just tried to update my sandboxing environmnent after long time > without update (i know it's bad...) and i'm facing a problem with multiple > gateway. > This environment work with 6 hypervisors (centos 8) and one manager on > dedicated server, all this baremetal have 2 interface in 2 différent > network protected by firewall. > All my hypervisords have 2 network for ovirt, one "ovirtmgmt" for > management (only SSH and internal admin stuff), the other "ovir_prod" for > console, migration, and default gateway. > > I've 3 hypervisors non updated which i can ping /ssh / ... (according to > iptables) on the two interface without problem. > But the 3 hypervisors just updated are accessible only on the "ovirt_prod" > interface. I'm looking inside ip route/ ip rules it seems to miss something. > I always configured my HV by ovirt gui so i does not understand what going > wrong. > > This is ip route/ip rules of my hv, it's like missing ip rules on non > working HV > The "route-ovirt_prod" file that does not exist on old HV. > > Working HV (centos 8.3 / vdsm 4.20.26.3-1) : > [root@drogo ~]# ip ru > 0: from all lookup local > 32000: from 10.100.126.0/24 lookup 174358038 > 32000: from all to 10.100.126.0/24 iif ovirtmgmt lookup 174358038 > 32000: from 10.5.7.0/24 lookup 168101654 > 32000: from all to 10.5.7.0/24 iif comte_prod lookup 168101654 > 32766: from all lookup main > 32767: from all lookup default > > [root@drogo ~]# ip rou > default via 10.5.7.254 dev comte_prod proto static metric 425 > 10.5.7.0/24 dev comte_prod proto kernel scope link src 10.5.7.22 > metric 425 > 10.100.126.0/24 dev ovirtmgmt proto kernel scope link src > 10.100.126.22 metric 426 > > Bugged HV (centos 8.4/ vdsm 4.40.70.6-1) > [root@balbo ~]# ip ru > 0: from all lookup local > 32766: from all lookup main > 32767: from all lookup default > > [root@balbo ~]# ip rou > default via 10.5.7.254 dev comte_prod proto static metric 425 > 10.5.6.0/26 dev enp4s0f1 proto kernel scope link src 10.5.6.6 metric > 100 linkdown > 10.5.7.0/24 dev comte_prod proto kernel scope link src 10.5.7.25 > metric 426 > 10.100.126.0/24 dev ovirtmgmt proto kernel scope link src > 10.100.126.25 metric 425 > > [root@bingo network-scripts]# cat route-ovirt_prod > ADDRESS0=0.0.0.0 > NETMASK0=0.0.0.0 > GATEWAY0=10.5.7.254 > OPTIONS0="table 254" > METRIC0=431 > > > > Than you for help :) > > -- > Lionel Caignec > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/3NSSFIKMKSMCTPVFSTEPLJJUXGRCXD7K/ > Hi, from the vdsm version it seems that the upgrade was from 4.2 to 4.4.7. Direct upgrade like that is not supported. There were a lot of changes 4.4 networking among other changes which might result in what you are experiencing. Please take a look at upgrade path from 4.2 to 4.4 in https://www.ovirt.org/documentation/upgrade_guide/index.html Thanks, Ales -- Ales Musil Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amu...@redhat.com IM: amusil <https://red.ht/sig>
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VS3SOQ3WQ3FG6FVYAO264IID26XJCOAX/
