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/
-------------------------------------------------------------------
<