-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
4.14.0, 4.15.0
-
None
-
No
-
uShift Sprint 244, uShift Sprint 245
-
2
-
False
-
-
Previously, a backup was created every time the MicroShift service started. These backups caused system backups to fail. Now, automated backups only occur on full system boots.
-
Bug Fix
This is a clone of issue OCPBUGS-22322. The following is the description of the original issue:
—
Description of problem:
If MicroShift service is restarted, it will create a backup for current boot (based on version file which contains that boot id). Because microshift does not update particular backup - it only creates new ones and deletes old ones, this behaviour will prevent a proper backup from being created when the host reboots.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. MicroShift svc is running 2. Note the contents of /var/lib/microshift/version 3. Check the contents of /var/lib/microshift-backups 4. Restart MicroShift svc 5. Check the contents of /var/lib/microshift-backups - new backup appeared 6. Restart MicroShift host 7. Check MicroShift's logs (sudo journalctl -u microshift -b 0): log is present "Backup already exists"
Actual results:
MicroShift creates backup on svc restart without host reboot which prevent proper backup from being created on system boot
Expected results:
MicroShift does not create backups without system reboot. For example, if boot_id obtained from /var/lib/microshift/version is the same as current boot ID, then skip the backup. It should only be created for past, previous boot
Additional info:
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
-
RHBA-2023:7472
Red Hat build of MicroShift 4.14.z bug fix and enhancement update