-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add timestamp to backup directory #299
Conversation
Why is this needed? The folder is deleted if it was there? And then it should not cause problems. |
Well if you cancel and restart for whatever reason, you will get a mixed state in there. alternatively we could delete and recreate the folder. |
But this is deleted right below the line you changed. 🤔 |
Hmm @schiessle had this on his own instance and with a customer |
What's in the updater log file? |
While looking at the code and thinking about the situation again I think the issue was the following:
This could be solved by keeping the previous backups and not replacing them. Either by adding a timestamp (like suggested by Joas) or a counter to the backups. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think this should make the update routine more robust and make sure that no backups are lost if the update process has to be restarted.
Can go. It's super unlikely that a folder that includes a timestamp already exist. |
Signed-off-by: Morris Jobke <[email protected]>
Signed-off-by: Morris Jobke <[email protected]>
Signed-off-by: Morris Jobke <[email protected]>
975d18f
to
decf787
Compare
/backport to stable19 |
The backport to stable19 failed. Please do this backport manually. |
No description provided.