Closed thimslugga closed 1 month ago
I believe that this issue is likely related to the issue fixed by #283 - the suse-migration-update-bootloader service incorrectly raced with the suse-migration-mount-system service and attempted to run commands under the /system-root chroot area before the appropriate file systems had been mounted.
The fix of the issue is included in the v2.0.40 release, which we are currently working on getting released through the official SUSE product release channels.
@rtamalin yes, it definitely looks like it's related to that PR.
With SLES 12 EoM quickly approaching, I am seeing more and more dist migrations happening so getting the new release will help reduce escalations for this red herring.
v2.0.40 release is done and I also agree with @rtamalin that this issue is related to the systemd services order which was fixed by Fergel. I'm closing this one. If you believe this is not fixed please re-open.
Thanks
SLES4SAP 12 SP5 (BYOS) -> 15 SP1 dist migration. Base OS was fully patched after launching. The dist migration did complete the upgrade to 15 SP1 despite the error. However this error was logged very early and causes end users to waste time triaging.