Description Dirk Schnick 2020-09-02 16:04:53 CEST

This will happen really rarely, but happened in a customer environment that uses opsi. The customer changes the default X environment after installation of the client PC and opsi seems to trigger this action simultaneous to the domain-join script. We should improve our script to prevent a traceback. The logfile:

2020-09-02 12:24:39,018 userinfo CRITICAL An error occurred: [Errno 2] No such file or directory: '/etc/X11/default-display-manager'. Please check /var/log/univention/domain-join-cli.log for more information.
2020-09-02 12:24:39,018 debugging CRITICAL [Errno 2] No such file or directory: '/etc/X11/default-display-manager'
Traceback (most recent call last):
  File "/usr/sbin/univention-domain-join-cli", line 187, in <module>
    distribution_joiner.check_if_join_is_possible_without_problems()
  File "/usr/lib/python3/dist-packages/univention_domain_join/distributions/ubuntu.py", line 76, in check_if_join_is_possible_without_problems
    if not self.skip_login_manager and LoginManagerConfigurator().configuration_conflicts():
  File "/usr/lib/python3/dist-packages/univention_domain_join/join_steps/login_manager_configurator.py", line 46, in configuration_conflicts
    login_manager = self.determin_used_login_manager()
  File "/usr/lib/python3/dist-packages/univention_domain_join/join_steps/login_manager_configurator.py", line 59, in determin_used_login_manager
    with open('/etc/X11/default-display-manager', 'r') as login_manager_file:
FileNotFoundError: [Errno 2] No such file or directory: '/etc/X11/default-display-manager'

I'm not sure if we should go on if the file does not exists or if we stop the join, as it is from my point of view no good idea to do other things on a machine simultaneous to the join. If we will stop, we should print a clear message instead of running into a traceback.