[Bug 1899964] Re: Failover of loadbalancer fails when Amphora master is missing

[Edward Hope-Morley]

Task originally tracked in storyboard:

https://storyboard.openstack.org/#!/story/2005072
https://storyboard.openstack.org/#!/story/2007847

Victoria patches are already included in Ubuntu packages for 7.0.0

Ussuri patches to be SRUd:
https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/ussuri+topic
:failover-refactor

Train patches to be SRUd:
https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/train+topic
:failover-refactor

** Description changed:

+ [Impact]
+ (from storyboard desciption) Currently if taskflow process is interrupted (during create/update/failover - node is rebooted or service is restarted) - loadbalancer will stuck in PENDING state.
+ Taskflow provides persistence module which allows to save flows state for recovery https://docs.openstack.org/taskflow/latest/user/persistence.html
+ Otherwise partially created/updated/deleted resources should be moved to ERROR state when service is up again. (like it is done in Cinder)
+ 
+ [Test Case]
+ 
+ [Regression Potential]
+ 
+ ------------------------------------------------------------------------
+ 
  Tried to failover a loadbalancer that has missing entries of amphora master.
  The loadbalancer went to ERROR state.
  
  OpenStack version: Train
  
  The fix is available in upstream as part of the Octavia Failover refactor patches in Train
  https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/train+topic:failover-refactor
  
  Verified with the upstream patches and it worked.

-- 
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/1899964

Title:
  Failover of loadbalancer fails when Amphora master is missing

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

Bug description:
  [Impact]
  (from storyboard desciption) Currently if taskflow process is interrupted (during create/update/failover - node is rebooted or service is restarted) - loadbalancer will stuck in PENDING state.
  Taskflow provides persistence module which allows to save flows state for recovery https://docs.openstack.org/taskflow/latest/user/persistence.html
  Otherwise partially created/updated/deleted resources should be moved to ERROR state when service is up again. (like it is done in Cinder)

  [Test Case]

  [Regression Potential]

  ------------------------------------------------------------------------

  Tried to failover a loadbalancer that has missing entries of amphora master.
  The loadbalancer went to ERROR state.

  OpenStack version: Train

  The fix is available in upstream as part of the Octavia Failover refactor patches in Train
  https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/train+topic:failover-refactor

  Verified with the upstream patches and it worked.

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