Bug 48708 - Traceback during installation of ucs-school-umc-installer
Traceback during installation of ucs-school-umc-installer
Status: CLOSED DUPLICATE of bug 48681
Product: UCS@school
Classification: Unclassified
Component: UMC - Installer
UCS@school 4.4
Other Linux
: P5 normal (vote)
: UCS@school 4.4 v2
Assigned To: UCS@school maintainers
:
Depends on: 48681
Blocks:
  Show dependency treegraph
 
Reported: 2019-02-19 14:27 CET by Ole Schwiegert
Modified: 2023-03-25 06:50 CET (History)
4 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?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.514
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

Note You need to log in before you can comment on or make changes to this bug.
Description Ole Schwiegert univentionstaff 2019-02-19 14:27:59 CET
+++ This bug was initially created as a clone of Bug #48681 +++

ucs-school-umc-installer (7.0.0-1A~4.4.0.201902141130) wird eingerichtet ...
Calling joinscript 35ucs-school-umc-installer.inst ...
2019-02-14 11:17:17.566500283+01:00 (in joinscript_init)
Object exists: cn=UMC,cn=univention,dc=nstx,dc=local
Object exists: cn=UMC,cn=policies,dc=nstx,dc=local
Object exists: cn=operations,cn=UMC,cn=univention,dc=nstx,dc=local
Object exists: cn=default-umc-all,cn=UMC,cn=policies,dc=nstx,dc=local
WARNING: cannot append cn=default-umc-all,cn=UMC,cn=policies,dc=nstx,dc=local to univentionPolicyReference, value exists
No modification: cn=Domain Admins,cn=groups,dc=nstx,dc=local
Object exists: cn=default-umc-users,cn=UMC,cn=policies,dc=nstx,dc=local
WARNING: cannot append cn=default-umc-users,cn=UMC,cn=policies,dc=nstx,dc=local to univentionPolicyReference, value exists
No modification: cn=Domain Users,cn=groups,dc=nstx,dc=local
Object exists: cn=schoolinstaller-all,cn=operations,cn=UMC,cn=univention,dc=nstx,dc=local
WARNING: cannot append cn=schoolinstaller-all,cn=operations,cn=UMC,cn=univention,dc=nstx,dc=local to allow, value exists
No modification: cn=default-umc-all,cn=UMC,cn=policies,dc=nstx,dc=local
2019-02-14 11:17:19.880653870+01:00 (in joinscript_save_current_version)
Joinscript 35ucs-school-umc-installer.inst finished with exitcode 0
Job for univention-management-console-server.service failed because the control process exited with error code.
See "systemctl status univention-management-console-server.service" and "journalctl -xe" for details.
invoke-rc.d: initscript univention-management-console-server, action "reload" failed.
Traceback (most recent call last):
  File "/usr/sbin/univention-management-console-acls", line 39, in <module>
    from univention.management.console.acl import Rule
ImportError: No module named management.console.acl
Trigger für python-support (1.0.15.18.201403132013) werden verarbeitet ...
Configuring ucsschool=4.4 v1
updating certificates for ucsschool=4.4 v1
File: /usr/share/univention-management-console/modules/apps.xml
Comment 1 Florian Best univentionstaff 2019-02-19 14:37:15 CET
What is this bug clone for?
Comment 2 Ole Schwiegert univentionstaff 2019-02-19 14:52:21 CET
Comment from Bug #48681:

We decided during a sprint meeting to just deactivate the problematic line in the post install script since it is not really necessary, but blocks the setup processes for the upcoming 4.4 release.

This bug is the clone for fixing this potential problem after 4.4v1.
A comment in the script itself, referring to this Bug was also added.
Comment 3 Ole Schwiegert univentionstaff 2019-02-20 08:46:15 CET
The problem described in this bug does not exist anymore due to the complete removal of the code section from the product.

As discussed with Daniel this problem is not part of UCS@school and thus this bug will be closed as well. Should this problem arise again, a new ticket shall be opened.

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