Activity log for bug #1815574

Date Who What changed Old value New value Message
2019-02-12 10:09:43 sapd bug added bug
2019-02-12 10:20:09 Dai Dang Van bug added subscriber luong tuan
2019-02-12 10:24:58 sapd description I have installed networking-ovn from ubuntu cloud repository. dpkg -l | grep ovn ii networking-ovn-common 5.0.0-0ubuntu2~cloud0 all OpenStack virtual network service - OVN driver ii python-networking-ovn 5.0.0-0ubuntu2~cloud0 all OpenStack virtual network service - OVN driver This is not latest version for rocky release ( latest is 5.0.1). So I clone repo (with branch stable/rocky) then upgrade manualy After that, I re-sync ovn database using this command: neutron-ovn-db-sync-util --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --ovn-neutron_sync_mode repair then all VM with Floating IPs loss 50% packets. Step to re-proceduce: 1) install networking-ovn from ubuntu repo stable/rocky 2) Create VM with FIPs 3) upgrade to latest branch stable/rocky 4) resync with mode repair Step to fix 1) stop ovsdb-nb-db 2) remove ovnnb_db.db 3) start ovsdb-nb-db 4) re-sync I have installed networking-ovn from ubuntu cloud repository.  dpkg -l | grep ovn ii networking-ovn-common 5.0.0-0ubuntu2~cloud0 all OpenStack virtual network service - OVN driver ii python-networking-ovn 5.0.0-0ubuntu2~cloud0 all OpenStack virtual network service - OVN driver This is not latest version for rocky release ( latest is 5.0.1). So I clone repo (with branch stable/rocky) then upgrade manualy After that, I re-sync ovn database using this command: neutron-ovn-db-sync-util --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --ovn-neutron_sync_mode repair then all VM with Floating IPs loss 50% packets. Step to re-proceduce: 1) install networking-ovn from ubuntu repo stable/rocky 2) Create VM with FIPs 3) upgrade to latest branch stable/rocky 4) resync with mode repair Step to fix 1) stop ovsdb-nb-db 2) remove ovnnb_db.db 3) start ovsdb-nb-db 4) re-sync Then re-associate FIPs 1) disassociate all floating IPs (release not required) 2) clear router's external gateway 3) re-add router's external gateway - all vms now have full connectivity 4) re-attach floating ips