This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 1813549 - Flow resumption
Summary: Flow resumption
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-octavia
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: ---
Assignee: Gregory Thiemonge
QA Contact: Bruna Bonguardo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-14 11:14 UTC by Carlos Goncalves
Modified: 2023-09-26 17:58 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-26 17:56:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack Storyboard 2005072 0 None None None 2020-03-14 11:14:51 UTC
OpenStack gerrit 647406 0 None MERGED Jobboard based controller 2021-01-27 14:32:43 UTC
OpenStack gerrit 816434 0 None MERGED Add parameters to configure amphorav2 driver 2022-03-16 10:12:41 UTC
OpenStack gerrit 820530 0 None MERGED Octavia Jobboard integration 2022-09-01 08:24:23 UTC
OpenStack gerrit 820668 0 None MERGED Include octavia task_flow manifest for octavia services 2022-06-02 16:20:07 UTC
OpenStack gerrit 833979 0 None MERGED Add parameters to configure amphorav2 driver 2022-03-17 15:18:06 UTC
Red Hat Issue Tracker OSP-29004 0 None None None 2023-09-26 17:58:05 UTC
Red Hat Issue Tracker   OSP-5191 0 None None None 2023-09-26 17:56:49 UTC

Description Carlos Goncalves 2020-03-14 11:14:51 UTC 
Currently when an Amphora type load balancer resource is under a change (create, update, delete, failover) and the controller service handling that provisioning flow shuts down abruptly, i.e. no graceful shutdown, the Taskflow flow is interrupted and the resource left stuck in PENDING_* provisioning state forever.

A workaround to unlock from this pending state is to manually change the provisioning status to ERROR and then either recreating (delete + create) or failover the load balancer or amphora.

This work allows sub-flow resumption of change actions by detecting a flow is not progressing and automatically re-assigning the flow to an alternate controller.

Note: This is an Ussuri priority upstream.

Taskflow provides a persistence module which allows flow resumption.
https://docs.openstack.org/taskflow/latest/user/persistence.html
https://docs.openstack.org/taskflow/latest/user/resumption.html

https://storyboard.openstack.org/#!/story/2005072
Note You need to log in before you can comment on or make changes to this bug.