USHIFT-1364: Don't overwrite health if backup wasn't created#1994
Conversation
|
@pmtk: This pull request references USHIFT-1364 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
There was a problem hiding this comment.
| echo "Not overwriting the health.json to retry backup on next boot" | |
| echo "Not overwriting the health.json, will retry backup on next boot" |
Does this change convey the same meaning? If so, it's a little more explicit.
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dhellmann, pmtk The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@pmtk: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Taking a backup is very important and we don't want to lose information that it should be done.
This change adds handling of situation where MicroShift is unhealthy because it couldn't make a backup and it should attempt to do it after reboot and after rollback: "don't overwrite 'backup' request if it wasn't created".