-
Bug
-
Resolution: Done
-
Major
-
0.1.19
-
False
-
-
False
-
-
Description of the problem:
When a workflow's sonataflow CR is deleted, the backstage plugin fails to update the catalog properly and the UI and backend start to report errors.
How reproducible: 100%
Steps to reproduce:
1. Have the orchestrator backstage instance running with workflows deployed.
2. Delete an existing workflow's sonataflow CR (oc delete sf <workflow name> -n sonataflow-infra or delete from the console.
3. Reload the orchestrator UI
Actual results: UI worklow tab results in 504 error:
Error
504: Error
Message
Request failed with status 504 Gateway Time-out, <html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.
</body></html>
Full Error as JSON
{
"error": {
"name": "Error",
"message": "Request failed with status 504 Gateway Time-out, <html><body><h1>504 Gateway Time-out</h1>\nThe server didn't respond in time.\n</body></html>\n"
},
"response": {
"statusCode": 504
}
}
In addition, the deleted workflow's (MTA) runs are still in the Workflow-runs tab:
Expected results: Workflow should be deleted without incident.
- depends on
-
FLPATH-1080 Disable abort when workflow execution does not exist
-
- Refinement
-