Stuck Pipeline - Orca with MySQL Editing the Database
Issue
After going through and attempting other resolutions for stuck pipelines, the pipeline may still remain and still continue to exist. Therefore, it is then necessary to take a look at the SQL backend and touch the database to remove the stuck execution
Cause
The execution is in such a state that executions from outside of Orca (e.g. the Swagger UI fix) cannot resolve the state of the pipeline. As a result, direct intervention on the MySQL Database backend for Orca is necessary.
PreviousStreaming Spinnaker Events to External Resources with Echo Event Filtering Plugin (PagerDuty)
NextSuggestions and Recommendations for configuring and optimizing Armory Spinnaker
Last updated
Was this helpful?