Bug 47019 - Update over multiple minor versions at once may lead to errors
Update over multiple minor versions at once may lead to errors
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Update - Release updates
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-05-16 14:24 CEST by Dirk Wiesenthal
Modified: 2021-05-14 16:34 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 7: Crash: Bug causes crash or data loss
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.240
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Wiesenthal univentionstaff 2018-05-16 14:24:03 CEST
I updated from UCS 4.1-5 to UCS 4.3-0 in "one step". Internally, univention-updater is called multiple times, but there is no break between the calls.

The update to 4.2-0 and up to 4.2-3 (current at the time) went without any errors. But the update to 4.3-0 failed because of multiple errors during package update.

If I remember correctly, this affected at least sshd and some kind of syslog daemon. I did not analyze this properly but I am quite sure that the problem was the switch to systemd. It could not really "adopt" the already running processes, got a failed state and could not restart them during the 4.3-0 package updates. (Thus, their postinst failed)

This will not happen again, as we will not switch to systemd twice. But in general, I think we would be much more safe if we would prevent a minor/major release update during PREUP if update/reboot/required is true - which I assume will always be the case after a first release update.

Not sure what this means for patchlevel releases. Maybe this would make multiple relase updates impossible as practically every patchlevel has its own kernel update.

Alternatively, one could hard check for --updateto "x+2" in univention-updater.

Or only check update/reboot/required in the PREUP of a minor/major update, but not for patchlevels.
Comment 1 Ingo Steuwer univentionstaff 2021-05-14 15:41:27 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.