Feature #2109
Refactor FAILED states
| Status: | Closed | Start date: | 06/07/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | OneFlow | |||
| Target version: | Release 4.2 | |||
| Resolution: | fixed | Pull request: |
Description
FAILED was kind of replaced with FAILED_DEPLOYING and _UNDEPLOYING, but it wasn't completely removed from the code.
FAILED_DEPLOYING _UNDEPLOYING should monitor the VMs, and recover automatically in some cases.
Associated revisions
Feature #2109: Remove FAILED state
Feature #2109: Monitor services in failed deployment and undeployment
In some cases, the operation continues automatically if the problem is fixed
Feature #2109: Recover for failed deployments now cleans VMs in failed and done
Feature #2109: Recover for failed shutdowns now retries to delete VMs
Feature #2109: Fix bug
Feature #2109: Recover for unknown now cleans VMs in failed and done
Feature #2109: Rename state UNKNOWN to WARNING
Feature #2109: Recover for unknown performs a boot for VMs in unknown
Feature #2109: A service enters the WARNING state only for VMs in FAILED or UNKNOWN
Feature #2109: VMs found in DONE are cleaned, and the cardinality lowered
Feature #2109: Recover action for any failed state deletes DONE and FAILED, and performs a boot on UNK VMs
Feature #2109: Allow shutdown from any state
History
#1
Updated by Carlos Martín about 8 years ago
- Tracker changed from Bug to Feature
- Subject changed from Remove FAILED state to Refactor FAILED states
- Description updated (diff)
#2
Updated by Carlos Martín about 8 years ago
- Status changed from New to Closed
- Assignee set to Carlos Martín
- Resolution set to fixed