Workflow can't be resumed

Description

There seems to be an issue with how node instances that are stuck in a transitory phase (CREATING / STARTING / CONFIGURING / STOPPING) are being handled. It is unclear how these fit into resumable workflows.

Our action items:
Figure out how such node instances fit into the picture
Decide on a reasonable approach of handling such node instances

Steps to Reproduce

Environment:
OS (CLI), HA cluster, cloud provider
------------------------------------

Steps to reproduce:
------------------
1.
2.
3.

Expected result:
---------------

Actual result:
-------------

Why Propose Close?

None

Activity

Show:
Alex Molev
August 18, 2020, 7:09 AM

I remember you fixed something in this area in 5.1. was it the same issue?

Michael Glokhman
August 18, 2020, 8:58 AM

Well, not exactly. My issue dealt with component/SR executions (which do not exist in 4.6) so it’s quite different

Assignee

Michael Glokhman

Reporter

Alex Molev

Labels

None

Severity

High

Target Version

4.6

Premium Only

yes

Found In Version

4.6

QA Owner

None

Bug Type

legacy bug

Customer Encountered

Yes

Customer Name

c312

Release Notes

no

Priority

High

Epic Link

Sprint

None

Priority

Critical
Configure