Bug 48679 - Broken join hook cannot be fixed on non-master systems automatically via e.g. an app update
Summary: Broken join hook cannot be fixed on non-master systems automatically via e.g....
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: Join (univention-join)
Version: UCS 4.4
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UCS maintainers
QA Contact: UCS maintainers
URL:
Keywords:
Depends on: 47940
Blocks:
  Show dependency treegraph
 
Reported: 2019-02-14 13:16 CET by Sönke Schwardt-Krummrich
Modified: 2024-06-27 12:09 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
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):
Customer ID:
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2019-02-14 13:16:02 CET
I think we have a problem with the new join hooks if a broken univention-join-hook of type join/pre-join or join/pre-joinscripts is registered in LDAP. This was just the case with a developing join hook from UCS@school:

In case of a faulty hook script (exitcode != 0) univention-join aborts the join process before executing the join scripts. For an app that is installed on a 
non-master, however, the join script is the only place to replace the defective join hook with a working variant. This means that if the join hook is broken, the app cannot automatically repair it with an app update.

I think we need an idea for a solution here.
Comment 1 Jan-Luca Kiok univentionstaff 2024-06-27 12:09:51 CEST
This issue has been filed against UCS 4.4.

UCS 4.4 is out of general maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

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