Package: debian-edu-config Version: 2.12.33 This issue is filed against debian-edu-config because it is a central piece in it and supplies the gosa-create-host script, however it is also a documentation bug and should be addressed in gosa as well. The DebianEdu documentation currently does not explicitly state whether the hostname when adding a new system via gosa should be fully qualified or not but it provides a screenshot with an example where the hostname is fully qualified "ws01.intern" (see attachment and https://jenkins.debian.net/userContent/debian-edu-doc/debian-edu-doc-en/debian-edu-bookworm-manual.html#idm1063). If a fully qualified hostname was given gosa will create an entry in LDAP with the following DN: cn=ws008,ou=workstations,ou=systems,dc=skole,dc=skolelinux,dc=no. However, the postcreate hook, i.e. the gosa-create-host script, expects the CN of the above entry to contain a non-qualified hostname and then tries to determine the fully qualified hostname first via DNS and then via LDAP which fails and causes the script to silently skip the creation of host and NFS Kerberos principals altogether. So the question here is how to handle this properly? I assume the non-qualified hostname is intended to be entered into gosa, in that case - the documentation should mention that and the screenshot should be updated - gosa should reject FQHN - the gosa-create-host script should be made more robust, exit with an error if the hostname contains a "." or the fully qualified hostname cannot be determined -- Guido Berhoerster
Attachment:
gosa_systems_edit_host.png
Description: PNG image
