Bug 42020 – univention-ad-connector: Failed to install

Bug 42020 - univention-ad-connector: Failed to install


Summary:	univention-ad-connector: Failed to install

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	AD Connector
Version:	UCS 4.1
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-08-17 16:24 CEST by Florian Best
Modified:	2019-01-03 07:19 CET (History)
CC List:	2 users (show)

See Also:	42425 43006
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?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	5: Blocking further progress on the daily work
User Pain:	0.343
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016111621000229, 2016081621000397, 2016081721000653, 2017100321000646
Bug group (optional):	External feedback
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

2016-08-17 16:24:49 CEST

We currently have mutliple feedbacks that the univention-ad-connector could not be installed during initial system setup.
Version: 4.1-3 errata234 (Vahr)

Einrichten der Software-Komponenten: univention-ad-connector: Failed to install

Comment 1 Erik Damrose

2016-08-17 16:32:03 CEST

Do we know if these were DVD installs or ucs-appliance installs?

Comment 2 Florian Best

2016-08-17 16:35:18 CEST

Another one:
Version: 4.1-3 errata234 (Vahr)

Remark: Any idea how to fix this ?

Traceback:
Configuring Active Directory connection:

Comment 3 Florian Best

2016-08-17 16:35:29 CEST

(In reply to Erik Damrose from comment #1)
> Do we know if these were DVD installs or ucs-appliance installs?
No idea.

Comment 4 Stefan Gohmann

2016-08-17 16:36:28 CEST

Erik, please have a look.

Comment 5 Erik Damrose

2016-08-17 17:47:38 CEST

I could not reproduce this. We need more information which medium was used and which options were chosen during installation

UCS Appliance 4.1-3:
OK: Join into AD domain
OK: Setup UCS domain, select AD Connector from system-setup

UCS 4.1-3 amd64 DVD:
OK: Join into AD domain
OK: Setup UCS domain, select AD Connector from system-setup

In all cases, univention-ad-connector was installed after system setup completed.

Comment 6 Florian Best

2016-08-17 18:56:42 CEST

Ticket#2016081621000397
Ticket#2016081721000653

Comment 7 Erik Damrose

2016-08-18 11:38:16 CEST

Maybe a repository error during installation, see bug 42025

Comment 8 Erik Damrose

2016-08-18 13:02:17 CEST

appliance
OK: no network, select ad-connector
OK: no network, select all components

dvd
OK: no network, select ad-connector
~ no network, select all components -> bug 42025

Comment 9 Erik Damrose

2016-08-19 10:40:01 CEST

If this occurs again and we have contact information, we should ask the feedback reporter about the installation method that was used (ucs appliance, dvd, app appliance...)

Comment 10 Florian Best

2016-08-19 10:49:40 CEST

Reported again, Ticket#2016081721000761

Comment 11 Florian Best

2016-09-16 10:16:07 CEST

Reported again, 4.1-3 errata268 (Vahr)

In combination with Bug #42425.

Comment 12 Florian Best

2016-11-17 17:27:54 CET

Reported again, 4.1-4 errata324 (Vahr)
There is a email address if you want to ask for logfiles. #2016111621000229

Comment 13 Florian Best

2017-10-12 20:30:32 CEST

Erik, there is an email address from the reporter, If you need info you can contact him.
#2017100321000646

Version: 4.2-2 errata189 (Lesum)

Remark: I was installing UCS as a basis for just a Samba-server, but it crashed during installation...

Comment 14 Stefan Gohmann

2019-01-03 07:19:06 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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