Activity log for bug #2016158

Date Who What changed Old value New value Message
2023-04-13 14:35:43 Rodolfo Alonso bug added bug
2023-04-14 10:29:32 Rodolfo Alonso neutron: importance Undecided Wishlist
2023-04-14 10:29:36 Rodolfo Alonso neutron: assignee Rodolfo Alonso (rodolfo-alonso-hernandez)
2023-06-09 17:30:52 OpenStack Infra neutron: status New In Progress
2023-06-29 08:42:39 Rodolfo Alonso description Then UUID of the "Chassis" register is the OVS "Openvswitch.external_ids:system-id" stored value. This value is created and stored in the filesystem [1]. The "ovn-controller" process uses this OVS system-id when creating the "Chassis" register. If this system-id is changed (for example during a host upgrade), the "ovn-controller" will create a new "Chassis" register once restarted. If by any circumstance, during this upgrade process (for example), the system-id is changed but the old "Chassis" register is not deleted from the OVN DB database by "ovn-controller" (the process is does not stop gracefully), Neutron will find two "Chassis" registers (and the corresponding "Chassis_Private") in the OVN SB database, both associated to the same host. The question this bug is proposing is: * Should Neutron handle this situation? * If yes, should Neutron perform a proactive OVN SB health action? * Should Neutron only inform to the user? (some users don't check the logs by default). [1]https://docs.openvswitch.org/en/latest/ref/ovs-ctl.8/ Then UUID of the "Chassis" register is the OVS "Openvswitch.external_ids:system-id" stored value. This value is created and stored in the filesystem [1]. The "ovn-controller" process uses this OVS system-id when creating the "Chassis" register. If this system-id is changed (for example during a host upgrade), the "ovn-controller" will create a new "Chassis" register once restarted. If by any circumstance, during this upgrade process (for example), the system-id is changed but the old "Chassis" register is not deleted from the OVN DB database by "ovn-controller" (the process is does not stop gracefully), Neutron will find two "Chassis" registers (and the corresponding "Chassis_Private") in the OVN SB database, both associated to the same host. The question this bug is proposing is: * Should Neutron handle this situation? * If yes, should Neutron perform a proactive OVN SB health action? * Should Neutron only inform to the user? (some users don't check the logs by default). [1]https://docs.openvswitch.org/en/latest/ref/ovs-ctl.8/ Related bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2181436
2023-06-29 14:33:42 Rodolfo Alonso neutron: status In Progress Fix Committed
2023-06-29 14:33:48 Rodolfo Alonso neutron: status Fix Committed Fix Released