I have noticed in the last few weeks that I have some Arm64 machines running MicroOS that are not rolling forward to the next versions of MicroOS. Automatic updates have not been working, apparently, and if I run "transactional-update" manually, it fails as well.
I have one system at:
and another system at:
Note that the one machine with the 20220613 snapshot was actually installed with an older image for demonstration purposes (a snapshot from May, I believe) and then pointed at a local copy of the 20220613 DVD for an "offline" update. So, it never saw the files from 20220628 to get synchronized to that point. (Long story).
Both systems go through all of the motions of an update (dracut, etc.), but the end of the "transactional-update" session looks like:
Since the last system boot core libraries or services have been updated. Reboot is suggested to ensure that your system benefits from these updates. 2022-09-02 17:21:11 Application returned with exit status 107. ERROR: zypper up on /.snapshots/27/snapshot failed with exit code 107! Use '--interactive' for manual problem resolution.
Warning: The following files were changed in the snapshot, but are shadowed by other mounts and will not be visible to the system: /.snapshots/27/snapshot/var/lib/systemd/catalog/database /.snapshots/27/snapshot/var/lib/systemd/random-seed /.snapshots/27/snapshot/var/lock /.snapshots/27/snapshot/var/mail Removing snapshot #27... 2022-09-02 17:21:12 tukit 4.0.1 started 2022-09-02 17:21:12 Options: abort 27 2022-09-02 17:21:12 Discarding snapshot 27. 2022-09-02 17:21:15 Transaction completed. transactional-update finished
Looking through the information written to the console, the only thing that claims to be an error is the following:
(265/313) Installing: suse-module-tools-16.0.22-1.1.aarch64 [...... /usr/bin/udevadm: error while loading shared libraries: libsystemd-shared-250.so: cannot open shared object file: No such file or directory ........... /usr/bin/udevadm: error while loading shared libraries: libsystemd-shared-250.so: cannot open shared object file: No such file or directory Running in chroot, ignoring command 'daemon-reload' done]
Everything else appears to be successful at installation.
Looking through the console log further, it is clear that libsystemd0-251.4-1.2.aarch64 was installed before the error occurred, which is why libsystemd-shared-250.so probably wasnt' around for suse-module-tools-16.0.22-1.1.aarch64 during its installation/upgrade.
Any suggestions on how to resolve this issue?
Further, there have been two releases of MicroOS aarch64 in the last few weeks and the two machines did not upgrade to either of those releases.
By the way, I have tried "transactional-update --interactive" and "transactional-update dup --interactive" with no difference in result and really no opportunity to change the results. "transactional-update dup --interactive" did prompt me for some responses.