Bug 52510 - Remove all redirects of output to /dev/null from univention-join
Summary: Remove all redirects of output to /dev/null from univention-join
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:
Blocks:
 
Reported: 2020-12-17 09:43 CET by Erik Damrose
Modified: 2025-02-05 09:28 CET (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.171
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Large environments, Usability
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 Erik Damrose univentionstaff 2020-12-17 09:43:45 CET
The output of several calls in univention-join is redirected to /dev/null. This makes debugging of join issues harder than is should be.

e.g. when joining a dc backup:
univention-scp "$DCPWD" -r \
    "${DCACCOUNT}@${DCNAME}:/var/lib/univention-ldap/notify/transaction" \
    "$USERTMP/tlog" >/dev/null 2>&1
if [ ! -e "$USERTMP/tlog" ]; then
    failed_message " FAILED: failed to copy /var/lib/univention-ldap/notify/transaction from the dc master. Please try again."
fi

This masks the issue, that the LDAP Account used to join the server was not present in the group "DC Backup Hosts" and was thus denied to read the file.
Comment 1 Jan-Luca Kiok univentionstaff 2025-02-05 09:28:35 CET
This issue has been filed against UCS 4.4.

UCS 4.4 is out of 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 information on how this issue is affecting you.