Bug 49299 - The Domain-Join fails but displays 'successful join'
Summary: The Domain-Join fails but displays 'successful join'
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: Univention Domain Join (Ubuntu)
Version: UCS 4.4
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UCS maintainers
QA Contact: UCS maintainers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-15 18:28 CEST by Nico Stöckigt
Modified: 2024-06-27 12:10 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.069
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019022721001399
Bug group (optional):
Customer ID: 31123
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 Nico Stöckigt univentionstaff 2019-04-15 18:28:11 CEST 
When joining with a "normal" Domain-Admin User the Join may fail due to the User is not member of the group 'DC Backup Slaves'. In that case the log does NOT contain any hint but instead prints out 'successfully joined'. However the client object is not created - this also is not visible in the server side logs.

The Domain-Join-Script should check if the used Join-User has sufficient rights.
Comment 1 Arvid Requate univentionstaff 2019-04-15 19:16:56 CEST 
"DC Backup Hosts"
Comment 2 Jan-Luca Kiok univentionstaff 2024-06-27 12:10:07 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.