When construction the ostree repo, ostree needs us to make a checksum(boot checksum) of kernel images and initramfs file stored in /usr/lib/ostree-boot. Each time to make a new deployment, that very checksum will be checked, once it is not correct, error occurred;
To avoid resetting target with INSVC patch installation, we just remount the /usr. While the principle is INSVC patch should not contain any modification on kernel or initramfs to avoid the checksum failure above;
The method to make the boot checksum is `cat file1 file2 file3 ... | sha256sum`, same file set with different order will lead to different checksum result. If this occurred when building INSVC patch without modification on kernel or initramfs, the boot checksum changed thus case the deploy failed.
When construction the ostree repo, ostree needs us to make a checksum(boot checksum) of kernel images and initramfs file stored in /usr/lib/ ostree- boot. Each time to make a new deployment, that very checksum will be checked, once it is not correct, error occurred;
To avoid resetting target with INSVC patch installation, we just remount the /usr. While the principle is INSVC patch should not contain any modification on kernel or initramfs to avoid the checksum failure above;
The method to make the boot checksum is `cat file1 file2 file3 ... | sha256sum`, same file set with different order will lead to different checksum result. If this occurred when building INSVC patch without modification on kernel or initramfs, the boot checksum changed thus case the deploy failed.