You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"tink workflow get/get by id" command returns the incorrect state for workflows.
Right now it always returns state as STATE_PENDING for all the workflows which is incorrect because if a workflow is running it should have state as STATE_RUNNING and if finished successfully, it should have state as STATE_SUCCESSFUL.
Expected Behaviour
"tink workflow get/get by id" command should return the current state for workflows.
Current Behaviour
Right now it always returns state as STATE_PENDING for all the workflows which is incorrect.
Possible Solution
Update the workflow state as soon as it started/finished/failed.
Operating System Linux (Ubuntu 1804):
How are you running Tinkerbell: Using Vagrant & VirtualBox
The text was updated successfully, but these errors were encountered:
"tink workflow get/get by id" command returns the incorrect state for workflows.
Right now it always returns state as STATE_PENDING for all the workflows which is incorrect because if a workflow is running it should have state as STATE_RUNNING and if finished successfully, it should have state as STATE_SUCCESSFUL.
Expected Behaviour
"tink workflow get/get by id" command should return the current state for workflows.
Current Behaviour
Right now it always returns state as STATE_PENDING for all the workflows which is incorrect.
Possible Solution
Update the workflow state as soon as it started/finished/failed.
Operating System Linux (Ubuntu 1804):
How are you running Tinkerbell: Using Vagrant & VirtualBox
The text was updated successfully, but these errors were encountered: