Bug 39950 – join not possible because computer already exists

Bug 39950 - join not possible because computer already exists


Summary:	join not possible because computer already exists

Status:	RESOLVED WORKSFORME

Product:	UCS
Classification:	Unclassified
Component:	UCS Net Installer
Version:	UCS 4.1
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-11-13 17:47 CET by Jürn Brodersen
Modified:	2015-11-23 14:27 CET (History)
CC List:	2 users (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 Jürn Brodersen

2015-11-13 17:47:59 CET

To enable the net installer for a computer it must be added under devices. But a join is not possible for an existing computer.
After deleting the computer the join is possible.

Comment 1 Stefan Gohmann

2015-11-14 10:39:03 CET

Did you use the same role? If you add the computer with the correct server role, it should work.

Comment 2 Jürn Brodersen

2015-11-23 14:27:45 CET

I had the wrong server role in my installation profile and I added the computer under ':/computers' and not under ':/computers/dc'.
(If you add a dc in the wrong container the join fails because the '30univention-appcenter.inst' script fails with a timeout.)

With the right settings the join works.

It may be a nice future to have more precise error messages if a join fails because an already existing LDAP object conflicts with the settings on the computer that wants to join. But I think that is only a problem if you use the net installer, because usually there would be no preexisting LDAP object.