Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/945140
Committed:
https://opendev.org/openstack/ovn-octavia-provider/commit/406665b2aea6655ab955084169363aa2a5464ce8
Submitter: "Zuul (22348)"
Branch: master
commit 406665b2aea6655ab955084169363aa2a5464ce8
Author: Fernando Royo <fr...@redhat.com>
Date: Thu Mar 20 17:54:49 2025 +0100
Fix OVN DB sync when syncing an OVN LB from scratch
When running octavia-ovn-db-sync-tool over a OVN LB that doesn't
exist on OVN NB DB the tool is reporting error status to Octavia API
on the last step.
This patch is fixing the dict reported to Octavia API that
was nested by error.
Closes-Bug: #2103518
Change-Id: Iac6ce4ed93e2c080050df87f81777bacb6b507c6
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2103518
Title:
[ovn-octavia-provider] OVN DB sync tool reporting error when OVN LB
doesn't exist
Status in neutron:
Fix Released
Bug description:
When running octavia-ovn-db-sync-tool over a OVN LB that doesn't exist
on OVN NB DB the tool is reporting error status to Octavia API on the
last step. Indeed mostly OVN LB is correctly sync, except if LB VIP is
associated with a FIP that is done in a post step to the feedback sent
to Octavia API. The error reported looks related to the body of the
request not well formed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2103518/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
