Bug 53363 – After preup.sh failed no joinscripts are executed anymore

Bug 53363 - After preup.sh failed no joinscripts are executed anymore


Summary:	After preup.sh failed no joinscripts are executed anymore

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Join (univention-join)
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2021-06-01 17:50 CEST by Florian Best
Modified:	2021-06-03 15:53 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
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
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Florian Best

2021-06-01 17:50:02 CEST

I tried to upgrade to UCS 5.0 which failed due to the preup.sh.
Therefore I decided to keep it UCS 4.4-8. But then joinscripts are no longer executed anymore:

e.g.:
ucs-school-umc-installer (7.0.1A~4.4.0.202105120922) wird eingerichtet ...
Calling joinscript 35ucs-school-umc-installer.inst ...
2021-05-14 03:11:56.840200100+02:00 (in joinscript_init)
A system update is currently being performed. The execution of the join script /usr/lib/univention-install/35ucs-school-umc-installer.inst is therefore postponed.                                                                            
Joinscript 35ucs-school-umc-installer.inst finished with exitcode 1

Comment 1 Florian Best

2021-06-01 17:51:38 CEST

# cat /var/lib/univention-updater/univention-updater.status
status=RUNNING
target_version=5.0-0
phase=PREUP
current_version=4.4-8
type=NET
next_version=5.0-0

Comment 2 Ingo Steuwer

2021-06-03 15:53:38 CEST

Is this issue reproducable? Does it affect every instance where an upgrade is stopped by checks in preup.sh? (if yes it should have a high priority)