yahoo-eng-team team mailing list archive

[Fernando Royo <2017216@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When a batch_update_members request [1] is sending not supported options
(e.g. monitor_X) over a member already existing or a new one the OVN-
provider applies the rest of changes for other members and skip the
member with the not supported option. For each action executed
(create/delete/update) an updated status is sent to Octavia API, and for
the skipped members and UnsupportedOptionError is replied.

The weird thing here is that Octavia API is not applying the other
member changes a soon as it receives the UnsupportedOptionError update
status for the skipped member, and at this way we are generating a out
of sync between the info in Octavia DB and the OVN NB DB side.

A reproducer is logged in
https://paste.openstack.org/show/bU4o2ylJOg7XLXgVXKps/

[1] https://docs.openstack.org/api-ref/load-
balancer/v2/?expanded=update-a-member-detail,list-pools-detail,create-
pool-detail,batch-update-members-detail#batch-update-members

** Affects: neutron
     Importance: Undecided
     Assignee: Fernando Royo (froyoredhat)
         Status: New


** Tags: ovn-octavia-provider

** 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/2017216

Title:
  [ovn-octavia-provider] batch member update generates out of sync with
  Octavia DB

Status in neutron:
  New

Bug description:
  When a batch_update_members request [1] is sending not supported
  options (e.g. monitor_X) over a member already existing or a new one
  the OVN-provider applies the rest of changes for other members and
  skip the member with the not supported option. For each action
  executed (create/delete/update) an updated status is sent to Octavia
  API, and for the skipped members and UnsupportedOptionError is
  replied.

  The weird thing here is that Octavia API is not applying the other
  member changes a soon as it receives the UnsupportedOptionError update
  status for the skipped member, and at this way we are generating a out
  of sync between the info in Octavia DB and the OVN NB DB side.

  A reproducer is logged in
  https://paste.openstack.org/show/bU4o2ylJOg7XLXgVXKps/

  [1] https://docs.openstack.org/api-ref/load-
  balancer/v2/?expanded=update-a-member-detail,list-pools-detail,create-
  pool-detail,batch-update-members-detail#batch-update-members

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2017216/+subscriptions