[ovirt-users] routing table and wrong ip rule attribution on hosts

Hi all, I 've finished migration from 4.4.4 to 4.4.9 and I'm facing a strange issue with routing table on my hosts: all IP addressed interfaces (and in particular gluster and migration ones that requiere an IP) are not part of the "254" or "0" usual ip rule. for instance: [root@fuego ~]# nmcli con sh gluster |grep ipv4.route-table ipv4.route-table:                       202179335 [root@fuego ~]# nmcli con sh migration |grep ipv4.route-table ipv4.route-table:                       316605387 but ovirtmgmt: [root@fuego ~]# nmcli con sh ovirtmgmt |grep ipv4.route-table ipv4.route-table:                       254 (main) and obviously the main route table is empty: [root@ ~]# ip ro default via 10.34.100.65 dev ovirtmgmt proto dhcp metric 425 10.34.100.0/24 dev ovirtmgmt proto kernel scope link src 10.34.100.116 metric 425 None of the concerned hosts can ping each other on such interface, and live migrations systematically fail. This behaviour is new with 4.4.9 and I don't know if it is a new (and not achevied) network feature introduced with centos stream to deal network filtering packets. A simple workaround would be "nmcli connection mod migration ipv4.route-table 0 && nmcli con up migration", but I'd like to understand why such  strange (and unuseful ?) rule table are now randomly attributed? -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr