Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionWelterlen Benoit
2022-04-07 13:49:57 UTC
Description of problem:
If we change the UUID of a partition, the new rescue ISO built by the cron.d job will not be able to restore the system due to a incoherency with data in the backup.
To reproduce the issue, change the UUID of the UEFI partition:
disklayout.conf before the change:
fs /dev/vda1 /boot/efi vfat uuid=ACC0-624F label= options=rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro
fstab before the change:
UUID=ACC0-624F /boot/efi vfat umask=0077,shortname=winnt 0 2
Then change the label:
mlabel -N 12345678 -i /dev/vda1 ::
Then, the cron.d job (or new systemd job) will recreate the rescue iso because the layout changed:
30 1 * * * root test -f /var/lib/rear/layout/disklayout.conf && /usr/sbin/rear checklayout || /usr/sbin/rear mkrescue
New disklayout.conf:
options=rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro
But the /etc/fstab file that will be used during the recover, and that should be patched, is still the one in the backup, thus the old one with old UUID.
And the patch will fail ... (without a warning :D).
And the system will not boot.
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. create a backup
2. change the UUID of UEFI partition
3. wait a day to get a new rescue iso built by crond job
Actual results:
The rescue ISO is not able to restore the layout+system
Expected results:
the system is recovered without issue
Additional info:
A rescue ISO should not be built if the required data in the backup is not updated also.
The recover of the system layout should rely on the data in the rescue ISO and not on the backup.
Thus all the files that should be patched to update the UUID should be embedded in the rescue.
Thanks !
Hello Benoit,
we discussed upstream an approach to prevent inconsistencies between backup and rescue system: the mkrescue and mkbackuponly command would check if the backup or rescue image (respectively) is outdated. This would mostly address the need for this change. The change to include all the files that need patching in the rescue image directly could be implemented as well, I am not entirely sure it is a good idea to duplicate the backups of some files though (i.e. having them both in the backup and in the rescue image). OTOH it would have the advantage of working correctly even with external backup methods. I will discuss this in the upstream project.
Hi Pavel,
Thanks a lot for the update. I followed the discussion at the beginning but then focused on other tasks.
From my point of view, the rescue ISO should be able to restore the layout of the server without the backup, thus it can be understandable that files required for that are included in the ISO, and such "system" files should not be overwritten by the backup data.
Thanks
Benoit
Comment 4RHEL Program Management
2023-09-21 23:36:22 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5RHEL Program Management
2023-09-21 23:40:10 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: If we change the UUID of a partition, the new rescue ISO built by the cron.d job will not be able to restore the system due to a incoherency with data in the backup. To reproduce the issue, change the UUID of the UEFI partition: disklayout.conf before the change: fs /dev/vda1 /boot/efi vfat uuid=ACC0-624F label= options=rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro fstab before the change: UUID=ACC0-624F /boot/efi vfat umask=0077,shortname=winnt 0 2 Then change the label: mlabel -N 12345678 -i /dev/vda1 :: Then, the cron.d job (or new systemd job) will recreate the rescue iso because the layout changed: 30 1 * * * root test -f /var/lib/rear/layout/disklayout.conf && /usr/sbin/rear checklayout || /usr/sbin/rear mkrescue New disklayout.conf: options=rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro But the /etc/fstab file that will be used during the recover, and that should be patched, is still the one in the backup, thus the old one with old UUID. And the patch will fail ... (without a warning :D). And the system will not boot. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. create a backup 2. change the UUID of UEFI partition 3. wait a day to get a new rescue iso built by crond job Actual results: The rescue ISO is not able to restore the layout+system Expected results: the system is recovered without issue Additional info: A rescue ISO should not be built if the required data in the backup is not updated also. The recover of the system layout should rely on the data in the rescue ISO and not on the backup. Thus all the files that should be patched to update the UUID should be embedded in the rescue. Thanks !