State after failed update is cumbersome #975
Assignees
Labels
Comments
sabbyanandan
modified the milestones:
Iteration 177 -> SCDF 2.7.0.M1,
Iteration 178 -> SCDF 2.7.0.M1
sabbyanandan
modified the milestones:
Iteration 178 -> SCDF 2.7.0.M1,
Iteration 179 -> SCDF 2.7.0.RC1
|
A similar problem appears to exist in Harness, Flux and maybe others. We will have to study how these various products are addressing this gap, to get some inspiration on solving it in Skipper. |
sabbyanandan
modified the milestones:
Iteration 179 -> SCDF 2.7.0.M2,
Iteration 180 -> SCDF 2.7.0.GA
sabbyanandan
modified the milestones:
Iteration 180 -> SCDF 2.7.0.RC1,
Iteration 181 -> SCDF 2.7.0.GA
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With a PR #972 we fixed issues where things doesn't really work anymore after an failed update. As that is now fixed there's a new issue where for user it's awkward to know what is a current state. Original release is not modified(as update cleaned up failed apps) but new release is added as FAILED.
We should somehow show that current release(kinda active) release is ok but to be able to indicate that there has been a FAILED release.
The text was updated successfully, but these errors were encountered: