Public bug reported:
When running octavia-ovn-db-sync-tool over a OVN LB that doesn't exit 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.
** Affects: neutron
Importance: Undecided
Assignee: Fernando Royo (froyoredhat)
Status: Confirmed
** Tags: ovn-octavia-provider
** Changed in: neutron
Status: New => Confirmed
** Changed in: neutron
Assignee: (unassigned) => Fernando Royo (froyoredhat)
--
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:
Confirmed
Bug description:
When running octavia-ovn-db-sync-tool over a OVN LB that doesn't exit
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
