a1exsh
a1exsh
And leads to the following problem (i.e. an endless loop at the last step): ``` 2017-05-18 13:05:25,477 INFO: Waiting for new instance to attach vol-1234abc channel 2: open failed: connect...
Concurrent update operations are not supported and probably not so easy to detect and guard against. We should at least document that to warn users against acting on the same...
Currently, any commit to the master branch triggers build if new docker images, most of them will be identical if we only change the create/update cluster script.
Currently `create` command produces colorful output by using click, while update is using `logger.INFO` mostly. Using click has some benefits, e.g. showing waiting progress in a more compact way.
Currently the failed state needs to be cleaned manually. We should prompt the user and do this automatically.
When performing a rolling update of a cluster, we terminate instances and create new ones, but in the process we may loose SNS notification topic if it was set previously...
In German, for example both "Neustart" (Restart) and "Ablehnen" (Decline) don't fit into the button width.  ⇒  Ideally, the translation could be improved, but at least it looks...
### Preliminary checks - [X] I've checked that there aren't [**other open issues**](https://github.com/ihhub/fheroes2/issues?q=is%3Aissue) on the same topic. - [X] I've checked that this issue is reproducible on the [**latest snapshot...
[Project board link](https://github.com/orgs/k8ssandra/projects/8/views/1?pane=issue&itemId=13951901) When one tries to delete a repair schedule, an error message like the following is shown: `Repair schedule c87975b0-4491-11e8-9602-9756d0798e38 currently running. Must be first stopped.` This is...