2310ddbc2c
Armada remediates releases stuck in FAILED status, if not protected, by purging and re-installing them. This implements the same for other non-DEPLOYED statuses. For these statuses it guards this with a best effort determination of whether a previous deployment of the release, either through armada or the helm CLI, is likely still pending based on whether it was last deployed within the chart's wait timeout. If it is deemed likely pending an error is raised, however this condition will eventually expire on future runs allowing for eventual remediation. Reasons why a release may get stuck in statuses other than DEPLOYED or FAILED include: 1. tiller crashed mid-deployment 2. tiller could not reach kubernetes to update the release state 3. running `helm delete <rel>` (without --purge) (DELETED status) Change-Id: Ia89cd59f056103dde47980a149c07a2984c4bbb4 |
||
|---|---|---|
| .. | ||
| exceptions | ||
| documents.rst | ||
| guide-build-armada-yaml.rst | ||
| guide-configure.rst | ||
| guide-helm-plugin.rst | ||
| guide-troubleshooting.rst | ||
| guide-use-armada.rst | ||
| index.rst | ||
| sampleconf.rst | ||
| samplepolicy.rst | ||