[Bug 1882657] Please test proposed package

[Corey Bryant]

Hello Hemanth, or anyone else affected,

Accepted octavia into stein-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:stein-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-stein-needed to verification-stein-done. If it does
not fix the bug for you, please add a comment stating that, and change
the tag to verification-stein-failed. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

** Changed in: cloud-archive/stein
       Status: Triaged => Fix Committed

** Tags added: verification-stein-needed

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1882657

Title:
  Batch update member to pool failed due to new_member is not exist in
  DB

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in Ubuntu Cloud Archive ussuri series:
  Fix Committed
Status in Ubuntu Cloud Archive victoria series:
  Fix Released
Status in octavia package in Ubuntu:
  Fix Released
Status in octavia source package in Focal:
  Fix Committed
Status in octavia source package in Groovy:
  Fix Released

Bug description:
  Original Upstream bug: https://storyboard.openstack.org/#!/story/2007581
  (The problem is observed in OpenStack Stein)

  Code review in progress (Upstream) -
  https://review.opendev.org/#/c/733670/

  
  ==========================================================================

  [Impact]
  Adding members to loadbalancer in batch mode fails and loadbalancers are
  stuck in pending_create state.
  This patch retries the read from DB 15 times to check if DB is populated properly or not.

  [Test Case]

  1. Reproducing the issue

  1a. Create 2 or more instances to add as members to loadbalancer
      (The issue can be reproduced if there is load on the machine, on my test environment able to reproduce with 2 members)
  1b. Create a loadbalancer, listener, pool and healthmonitor
      openstack loadbalancer create --name lb1 --vip-subnet-id private_subnet
      openstack loadbalancer listener create --name listener1 --protocol HTTP --protocol-port 80 lb1
      openstack loadbalancer pool create --name pool1 --lb-algorithm ROUND_ROBIN --listener listener1 --protocol HTTP
      openstack loadbalancer healthmonitor create --name hm1 --delay 5 --max-retries 4 --timeout 10 --type HTTP --url-path / pool1
  1c. Create a token
      AUTH_TOKEN=$(openstack token issue  -c id -f value)
  1d. Prepare a file members.json based on Request example in the below link
      https://docs.openstack.org/api-ref/load-balancer/v2/?expanded=batch-update-members-detail#batch-update-members
  1e. Add members in batch mode
      curl -X PUT -H "Content-Type: application/json" -H "X-Auth-Token: $AUTH_TOKEN" -d @members.json http://<ip>:<port>/v2.0/lbaas/pools/<pool_id>/members
  1f. Check loadbalancer show. This will be in pending_create state in non-working case
      openstack loadbalancer show lb1

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1f. Loadbalancer should be in ACTIVE state

  
  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of octavia service for few milliseconds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1882657/+subscriptions