| 2023-08-08 14:17:07 |
Lucas Alvares Gomes |
bug |
|
|
added bug |
| 2023-08-08 14:25:51 |
OpenStack Infra |
neutron: status |
Confirmed |
In Progress |
|
| 2023-08-15 14:10:33 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
| 2023-08-21 19:51:56 |
OpenStack Infra |
tags |
ovn |
in-stable-zed ovn |
|
| 2023-08-21 19:52:01 |
OpenStack Infra |
tags |
in-stable-zed ovn |
in-stable-yoga in-stable-zed ovn |
|
| 2023-08-21 19:52:06 |
OpenStack Infra |
tags |
in-stable-yoga in-stable-zed ovn |
in-stable-xena in-stable-yoga in-stable-zed ovn |
|
| 2023-08-21 19:52:12 |
OpenStack Infra |
tags |
in-stable-xena in-stable-yoga in-stable-zed ovn |
in-stable-wallaby in-stable-xena in-stable-yoga in-stable-zed ovn |
|
| 2023-08-22 13:57:31 |
OpenStack Infra |
tags |
in-stable-wallaby in-stable-xena in-stable-yoga in-stable-zed ovn |
in-stable-victoria in-stable-wallaby in-stable-xena in-stable-yoga in-stable-zed ovn |
|
| 2023-08-22 14:26:11 |
OpenStack Infra |
tags |
in-stable-victoria in-stable-wallaby in-stable-xena in-stable-yoga in-stable-zed ovn |
in-stable-ussuri in-stable-victoria in-stable-wallaby in-stable-xena in-stable-yoga in-stable-zed ovn |
|
| 2023-11-06 20:58:59 |
Corey Bryant |
bug task added |
|
neutron (Ubuntu) |
|
| 2023-11-06 20:59:20 |
Corey Bryant |
nominated for series |
|
Ubuntu Lunar |
|
| 2023-11-06 20:59:20 |
Corey Bryant |
bug task added |
|
neutron (Ubuntu Lunar) |
|
| 2023-11-06 21:01:48 |
Corey Bryant |
neutron (Ubuntu): status |
New |
Fix Released |
|
| 2023-11-06 21:01:53 |
Corey Bryant |
neutron (Ubuntu Lunar): status |
New |
Triaged |
|
| 2023-11-06 21:01:55 |
Corey Bryant |
neutron (Ubuntu Lunar): importance |
Undecided |
Medium |
|
| 2023-11-06 21:02:50 |
Corey Bryant |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-11-06 21:02:50 |
Corey Bryant |
bug task added |
|
neutron (Ubuntu Jammy) |
|
| 2023-11-06 21:03:05 |
Corey Bryant |
neutron (Ubuntu Jammy): status |
New |
Triaged |
|
| 2023-11-06 21:03:07 |
Corey Bryant |
neutron (Ubuntu Jammy): importance |
Undecided |
Medium |
|
| 2023-11-06 21:03:20 |
Corey Bryant |
bug task added |
|
cloud-archive |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
nominated for series |
|
cloud-archive/antelope |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
bug task added |
|
cloud-archive/antelope |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
nominated for series |
|
cloud-archive/ussuri |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
bug task added |
|
cloud-archive/ussuri |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
nominated for series |
|
cloud-archive/xena |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
bug task added |
|
cloud-archive/xena |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
nominated for series |
|
cloud-archive/wallaby |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
bug task added |
|
cloud-archive/wallaby |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
nominated for series |
|
cloud-archive/yoga |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
bug task added |
|
cloud-archive/yoga |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
nominated for series |
|
cloud-archive/zed |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
bug task added |
|
cloud-archive/zed |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
nominated for series |
|
cloud-archive/victoria |
|
| 2023-11-06 21:04:38 |
Corey Bryant |
bug task added |
|
cloud-archive/victoria |
|
| 2023-11-06 21:04:49 |
Corey Bryant |
cloud-archive: status |
New |
Fix Released |
|
| 2023-11-06 21:05:28 |
Corey Bryant |
nominated for series |
|
Ubuntu Focal |
|
| 2023-11-06 21:05:28 |
Corey Bryant |
bug task added |
|
neutron (Ubuntu Focal) |
|
| 2023-11-06 21:05:42 |
Corey Bryant |
neutron (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2023-11-06 21:05:42 |
Corey Bryant |
neutron (Ubuntu Focal): status |
New |
Triaged |
|
| 2023-11-06 21:05:51 |
Corey Bryant |
cloud-archive/antelope: importance |
Undecided |
Medium |
|
| 2023-11-06 21:05:51 |
Corey Bryant |
cloud-archive/antelope: status |
New |
Triaged |
|
| 2023-11-06 21:06:02 |
Corey Bryant |
cloud-archive/ussuri: importance |
Undecided |
Medium |
|
| 2023-11-06 21:06:02 |
Corey Bryant |
cloud-archive/ussuri: status |
New |
Triaged |
|
| 2023-11-06 21:06:24 |
Corey Bryant |
cloud-archive/victoria: importance |
Undecided |
Medium |
|
| 2023-11-06 21:06:24 |
Corey Bryant |
cloud-archive/victoria: status |
New |
Triaged |
|
| 2023-11-06 21:06:33 |
Corey Bryant |
cloud-archive/wallaby: importance |
Undecided |
Medium |
|
| 2023-11-06 21:06:33 |
Corey Bryant |
cloud-archive/wallaby: status |
New |
Triaged |
|
| 2023-11-06 21:06:42 |
Corey Bryant |
cloud-archive/xena: importance |
Undecided |
Medium |
|
| 2023-11-06 21:06:42 |
Corey Bryant |
cloud-archive/xena: status |
New |
Triaged |
|
| 2023-11-06 21:06:51 |
Corey Bryant |
cloud-archive/yoga: importance |
Undecided |
Medium |
|
| 2023-11-06 21:06:51 |
Corey Bryant |
cloud-archive/yoga: status |
New |
Triaged |
|
| 2023-11-06 21:06:59 |
Corey Bryant |
cloud-archive/zed: importance |
Undecided |
Medium |
|
| 2023-11-06 21:06:59 |
Corey Bryant |
cloud-archive/zed: status |
New |
Triaged |
|
| 2023-11-15 18:39:47 |
Corey Bryant |
description |
Reported at: https://bugzilla.redhat.com/show_bug.cgi?id=2225156
The ovn-db-sync script does not check if the router ports are actually out-of-sync before adding it to the list of ports that needs to be updated, this can create red herring problems by introducing an irrelevant piece of information [0] in the sync report (specially when ran in "log" mode) making the user think that the databases might be out-of-sync even when it is not.
Looking at the code [1] we can see that the comment talks about checking the networks and ipv6_ra_configs changes but it does neither; instead, it adds every router port to the list of ports that needs to be updated.
<snipet>
# We dont have to check for the networks and
# ipv6_ra_configs values. Lets add it to the
# update_lrport_list. If they are in sync, then
# update_router_port will be a no-op.
update_lrport_list.append(db_router_ports[lrport])
</snipet>
This LP is about changing this behavior and checking for such differences in the router ports before marking them to be updated.
[0]
2023-07-24 11:46:31.391 952358 WARNING networking_ovn.ovn_db_sync [req-1081a8a6-82dd-431c-a2ab-f58741dc1677 - - - - -] Router Port port_id=f164c0f1-8ac8-4c45-bba9-8c723a30c701 needs to be updated for networks changed
[1]
https://github.com/openstack/neutron/blob/c453813d0664259c4da0d132f224be2eebe70072/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_db_sync.py#L553-L557 |
Reported at: https://bugzilla.redhat.com/show_bug.cgi?id=2225156
The ovn-db-sync script does not check if the router ports are actually out-of-sync before adding it to the list of ports that needs to be updated, this can create red herring problems by introducing an irrelevant piece of information [0] in the sync report (specially when ran in "log" mode) making the user think that the databases might be out-of-sync even when it is not.
Looking at the code [1] we can see that the comment talks about checking the networks and ipv6_ra_configs changes but it does neither; instead, it adds every router port to the list of ports that needs to be updated.
<snipet>
# We dont have to check for the networks and
# ipv6_ra_configs values. Lets add it to the
# update_lrport_list. If they are in sync, then
# update_router_port will be a no-op.
update_lrport_list.append(db_router_ports[lrport])
</snipet>
This LP is about changing this behavior and checking for such differences in the router ports before marking them to be updated.
[0]
2023-07-24 11:46:31.391 952358 WARNING networking_ovn.ovn_db_sync [req-1081a8a6-82dd-431c-a2ab-f58741dc1677 - - - - -] Router Port port_id=f164c0f1-8ac8-4c45-bba9-8c723a30c701 needs to be updated for networks changed
[1]
https://github.com/openstack/neutron/blob/c453813d0664259c4da0d132f224be2eebe70072/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_db_sync.py#L553-L557
===== Ubuntu SRU Details =====
[Impact]
See bug description above.
[Test Case]
Deploy openstack with OVN and multiple routers. Run the ovn-db-sync script and ensure router ports that are not out of sync are not marked to be updated.
[Regression Potential]
If the _is_router_port_changed() function had a bug there would be potential for ports to be filtered out that need updating. Presumably this is not the case, but that is a theoritical potential for regression. All of these patches have already landed in the corresponding upsream branches. |
|
| 2023-11-15 18:41:14 |
Corey Bryant |
description |
Reported at: https://bugzilla.redhat.com/show_bug.cgi?id=2225156
The ovn-db-sync script does not check if the router ports are actually out-of-sync before adding it to the list of ports that needs to be updated, this can create red herring problems by introducing an irrelevant piece of information [0] in the sync report (specially when ran in "log" mode) making the user think that the databases might be out-of-sync even when it is not.
Looking at the code [1] we can see that the comment talks about checking the networks and ipv6_ra_configs changes but it does neither; instead, it adds every router port to the list of ports that needs to be updated.
<snipet>
# We dont have to check for the networks and
# ipv6_ra_configs values. Lets add it to the
# update_lrport_list. If they are in sync, then
# update_router_port will be a no-op.
update_lrport_list.append(db_router_ports[lrport])
</snipet>
This LP is about changing this behavior and checking for such differences in the router ports before marking them to be updated.
[0]
2023-07-24 11:46:31.391 952358 WARNING networking_ovn.ovn_db_sync [req-1081a8a6-82dd-431c-a2ab-f58741dc1677 - - - - -] Router Port port_id=f164c0f1-8ac8-4c45-bba9-8c723a30c701 needs to be updated for networks changed
[1]
https://github.com/openstack/neutron/blob/c453813d0664259c4da0d132f224be2eebe70072/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_db_sync.py#L553-L557
===== Ubuntu SRU Details =====
[Impact]
See bug description above.
[Test Case]
Deploy openstack with OVN and multiple routers. Run the ovn-db-sync script and ensure router ports that are not out of sync are not marked to be updated.
[Regression Potential]
If the _is_router_port_changed() function had a bug there would be potential for ports to be filtered out that need updating. Presumably this is not the case, but that is a theoritical potential for regression. All of these patches have already landed in the corresponding upsream branches. |
Reported at: https://bugzilla.redhat.com/show_bug.cgi?id=2225156
The ovn-db-sync script does not check if the router ports are actually out-of-sync before adding it to the list of ports that needs to be updated, this can create red herring problems by introducing an irrelevant piece of information [0] in the sync report (specially when ran in "log" mode) making the user think that the databases might be out-of-sync even when it is not.
Looking at the code [1] we can see that the comment talks about checking the networks and ipv6_ra_configs changes but it does neither; instead, it adds every router port to the list of ports that needs to be updated.
<snipet>
# We dont have to check for the networks and
# ipv6_ra_configs values. Lets add it to the
# update_lrport_list. If they are in sync, then
# update_router_port will be a no-op.
update_lrport_list.append(db_router_ports[lrport])
</snipet>
This LP is about changing this behavior and checking for such differences in the router ports before marking them to be updated.
[0]
2023-07-24 11:46:31.391 952358 WARNING networking_ovn.ovn_db_sync [req-1081a8a6-82dd-431c-a2ab-f58741dc1677 - - - - -] Router Port port_id=f164c0f1-8ac8-4c45-bba9-8c723a30c701 needs to be updated for networks changed
[1]
https://github.com/openstack/neutron/blob/c453813d0664259c4da0d132f224be2eebe70072/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_db_sync.py#L553-L557
===== Ubuntu SRU Details =====
[Impact]
See bug description above.
[Test Case]
Deploy openstack with OVN and multiple routers. Run the ovn-db-sync script and ensure router ports that are not out of sync are not marked to be updated.
[Where problems could occur]
If the _is_router_port_changed() function had a bug there would be potential for ports to be filtered out that need updating. Presumably this is not the case, but that is a theoritical potential for where problems could occur. All of these patches have already landed in the corresponding upsream branches. |
|
| 2023-11-15 19:05:14 |
Corey Bryant |
description |
Reported at: https://bugzilla.redhat.com/show_bug.cgi?id=2225156
The ovn-db-sync script does not check if the router ports are actually out-of-sync before adding it to the list of ports that needs to be updated, this can create red herring problems by introducing an irrelevant piece of information [0] in the sync report (specially when ran in "log" mode) making the user think that the databases might be out-of-sync even when it is not.
Looking at the code [1] we can see that the comment talks about checking the networks and ipv6_ra_configs changes but it does neither; instead, it adds every router port to the list of ports that needs to be updated.
<snipet>
# We dont have to check for the networks and
# ipv6_ra_configs values. Lets add it to the
# update_lrport_list. If they are in sync, then
# update_router_port will be a no-op.
update_lrport_list.append(db_router_ports[lrport])
</snipet>
This LP is about changing this behavior and checking for such differences in the router ports before marking them to be updated.
[0]
2023-07-24 11:46:31.391 952358 WARNING networking_ovn.ovn_db_sync [req-1081a8a6-82dd-431c-a2ab-f58741dc1677 - - - - -] Router Port port_id=f164c0f1-8ac8-4c45-bba9-8c723a30c701 needs to be updated for networks changed
[1]
https://github.com/openstack/neutron/blob/c453813d0664259c4da0d132f224be2eebe70072/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_db_sync.py#L553-L557
===== Ubuntu SRU Details =====
[Impact]
See bug description above.
[Test Case]
Deploy openstack with OVN and multiple routers. Run the ovn-db-sync script and ensure router ports that are not out of sync are not marked to be updated.
[Where problems could occur]
If the _is_router_port_changed() function had a bug there would be potential for ports to be filtered out that need updating. Presumably this is not the case, but that is a theoritical potential for where problems could occur. All of these patches have already landed in the corresponding upsream branches. |
Reported at: https://bugzilla.redhat.com/show_bug.cgi?id=2225156
The ovn-db-sync script does not check if the router ports are actually out-of-sync before adding it to the list of ports that needs to be updated, this can create red herring problems by introducing an irrelevant piece of information [0] in the sync report (specially when ran in "log" mode) making the user think that the databases might be out-of-sync even when it is not.
Looking at the code [1] we can see that the comment talks about checking the networks and ipv6_ra_configs changes but it does neither; instead, it adds every router port to the list of ports that needs to be updated.
<snipet>
# We dont have to check for the networks and
# ipv6_ra_configs values. Lets add it to the
# update_lrport_list. If they are in sync, then
# update_router_port will be a no-op.
update_lrport_list.append(db_router_ports[lrport])
</snipet>
This LP is about changing this behavior and checking for such differences in the router ports before marking them to be updated.
[0]
2023-07-24 11:46:31.391 952358 WARNING networking_ovn.ovn_db_sync [req-1081a8a6-82dd-431c-a2ab-f58741dc1677 - - - - -] Router Port port_id=f164c0f1-8ac8-4c45-bba9-8c723a30c701 needs to be updated for networks changed
[1]
https://github.com/openstack/neutron/blob/c453813d0664259c4da0d132f224be2eebe70072/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_db_sync.py#L553-L557
===== Ubuntu SRU Details =====
[Impact]
See bug description above.
[Test Case]
Deploy openstack with OVN and multiple routers. Run the ovn-db-sync script and ensure router ports that are not out of sync are not marked to be updated.
[Where problems could occur]
If the _is_router_port_changed() function had a bug there would be potential for ports to be filtered out that need updating. Presumably this is not the case, but that is a theoritical potential for where problems could occur. All of these patches have already landed in the corresponding upstream branches. |
|
| 2023-11-15 20:27:26 |
Brian Haley |
bug |
|
|
added subscriber Brian Haley |
