Bug 31633 – schoolinstaller does not recognize errors

Bug 31633 - schoolinstaller does not recognize errors


Summary:	schoolinstaller does not recognize errors

Status:	CLOSED DUPLICATE of bug 34058

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - Installer
Version:	UCS@school 3.1 R2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS@school 3.x
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:	31128
Blocks:
	Show dependency tree / graph

Reported:	2013-06-04 12:31 CEST by Florian Best
Modified:	2023-06-12 15:39 CEST (History)
CC List:	3 users (show)

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?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Usability
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

2013-06-04 12:31:29 CEST

The fix for Bug #31128 implements an error message and module offers an option to "repeat". After clicking on repeat i got the message that UCS@School is already configured because the packages are installed on the system.

+++ This bug was initially created as a clone of Bug #31128 +++

The schoolinstaller displayed that the installation was successful, but it wasn't.

from the log
====
22.04.13 07:04:38.975  MODULE      ( PROCESS ) : Installed ucs-school-slave
22.04.13 07:04:38.978  MODULE      ( PROCESS ) : Processing triggers for python-support ...
22.04.13 07:04:38.978  MODULE      ( PROCESS ) : Running post-installation trigger python-support
22.04.13 07:04:43.189  MODULE      ( WARN    ) : Could not successfully move the slave DC into its correct OU structure:
ERROR: cannot move domaincontroller slave with hostname "slave" to OU "errataschule"
ERROR: The system has no LDAP access to the OU
====

to reproduce this: create an OU with wrong slave servername and join the school-slave with the schoolinstaller module

Comment 1 Stefan Gohmann

2013-06-10 19:43:56 CEST

Does this happen often?

Comment 2 Alexander Kläser

2013-06-11 12:27:12 CEST

Good question, during normal usage this probably does not happen, only in case of a misconfiguration. This is probably not the case if the installation is being done from the scratch.

Comment 3 Florian Best

2016-11-16 12:03:58 CET


*** This bug has been marked as a duplicate of bug 34058 ***