transactional-update failing and destroying snapshot on zypper exit code 107
Hello!
I'd be curious if I'm the only one running into the following, when
doing, for instance, `transactional-update dup`, or similar):
[zypper downloading and installing packages]
There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs.
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-05-16 10:23:35 Application returned with exit status 107.
ERROR: zypper --no-cd dup on /.snapshots/269/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/269/snapshot/var/lib/systemd/catalog/database
/.snapshots/269/snapshot/var/lib/systemd/random-seed
/.snapshots/269/snapshot/var/lib/dbus/machine-id
/.snapshots/269/snapshot/var/lib/sgml/CATALOG.iso_ent
/.snapshots/269/snapshot/var/mail
Removing snapshot #269...
2022-05-16 10:23:37 tukit 4.0.0~rc2 started
2022-05-16 10:23:37 Options: abort 269
2022-05-16 10:23:38 Discarding snapshot 269.
2022-05-16 10:23:41 Transaction completed.
transactional-update finished
Basically, the dup went well, but zypper is informing us that some
service reload and/or a reboot is necessary.
Now, this is of course not particularly useful as a message, on a t-u
based system, as we're going to reboot anyway. But the real problem
seems to me to be that zypper itself returns 107, when printing that
message.
And it also seems to me that t-u interpret such return code as failure
and destroys the snapshot, which does not seem right.
FTR, this is happening to me on my MicroOS Desktop box, but it looks a
t-u general issue to me. Or is it me that am missing something or doing
something wrong?
Thanks and Regards
--
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<
Am 16.05.22 um 11:10 Uhr schrieb Dario Faggioli:
Hello!
I'd be curious if I'm the only one running into the following, when doing, for instance, `transactional-update dup`, or similar):
[zypper downloading and installing packages] There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs.
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-05-16 10:23:35 Application returned with exit status 107. ERROR: zypper --no-cd dup on /.snapshots/269/snapshot failed with exit code 107! [...] Basically, the dup went well, but zypper is informing us that some service reload and/or a reboot is necessary.
Now, this is of course not particularly useful as a message, on a t-u based system, as we're going to reboot anyway. But the real problem seems to me to be that zypper itself returns 107, when printing that message.
As Thorsten said already: return code 107 is ZYPPER_EXIT_INF_RPM_SCRIPT_FAILED, so that's a real error condition. What you are thinking about are 102 and 103 (ZYPPER_EXIT_INF_REBOOT_NEEDED / ZYPPER_EXIT_INF_RESTART_NEEDED), and these are ignored as expected. Cheers, Ignaz
On Wed, 2022-05-18 at 08:54 +0200, Ignaz Forster wrote:
Am 16.05.22 um 11:10 Uhr schrieb Dario Faggioli:
Now, this is of course not particularly useful as a message, on a t-u based system, as we're going to reboot anyway. But the real problem seems to me to be that zypper itself returns 107, when printing that message.
As Thorsten said already: return code 107 is ZYPPER_EXIT_INF_RPM_SCRIPT_FAILED, so that's a real error condition.
Mmm... wow, that's quite an oversight! Sorry for the noise. :-(
What you are thinking about are 102 and 103 (ZYPPER_EXIT_INF_REBOOT_NEEDED / ZYPPER_EXIT_INF_RESTART_NEEDED), and these are ignored as expected.
Right. The update was happening in a terminal, and I was giving it a
look (albeit, while doing other things). It did not stop because of any
error, nor I saw any of them pass, so I thought it could have been the
"restart service" thing.
Instead, I should have checked both the log and the actual error codes.
Sorry again, thanks and Regards
--
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<
participants (2)
-
Dario Faggioli -
Ignaz Forster