Univention Bugzilla – Bug 53156
Network settings: Changes via Network settings do not change corresponding LDAP entries
Last modified: 2021-05-25 15:58:41 CEST
Changes via Network settings module do not change corresponding LDAP entries. Example: After changing the IP adress of a server via System > Network settings, LDAP still shows the old IP adress. However, the server can be reached under the new IP adress and the network interface is correctly updated. This behaviour does not occur on UCS 4 systems. Making changes via Network settings there automatically updates corresponding LDAP entries.
When Samba4 is installed the issue does not occur anymore.
When I changed the IPv4 address of the system (ox12.uni.dtr, old IP 10.200.3.12, new IP 10.200.3.13) in UCS 4.4, the domain DNS server (itself) as well and the external DNS server from 10.200.3.1 to 192.168.0.124. I got the following pop up: ---------------------------------------------------------------------------- Die folgenden Änderungen werden auf das System übertragen: Domänen-DNS-Server: 10.200.3.13 Externer DNS-Server: 192.168.0.124 Netzwerkgeräte: Verändert: ens3 (Ethernet): Statisch: 10.200.3.13/24 ---------------------------------------------------------------------------- Then the following LDAP entries were changed: ---------------------------------------------------------------------------- dn: zoneName=uni.dtr,cn=dns,dc=uni,dc=dtr -sOARecord: ox12.uni.dtr. root.uni.dtr. 9 28800 7200 604800 10800 +sOARecord: ox12.uni.dtr. root.uni.dtr. 11 28800 7200 604800 10800 dn: zoneName=3.200.10.in-addr.arpa,cn=dns,dc=uni,dc=dtr -sOARecord: ox12.uni.dtr. root.uni.dtr. 2 28800 7200 604800 10800 +sOARecord: ox12.uni.dtr. root.uni.dtr. 4 28800 7200 604800 10800 dn: relativeDomainName=ox12,zoneName=uni.dtr,cn=dns,dc=uni,dc=dtr -aRecord: 10.200.3.12 +aRecord: 10.200.3.13 dn: relativeDomainName=ucs-sso,zoneName=uni.dtr,cn=dns,dc=uni,dc=dtr -aRecord: 10.200.3.12 +aRecord: 10.200.3.13 -dn: relativeDomainName=12,zoneName=3.200.10.in-addr.arpa,cn=dns,dc=uni,dc=dtr +dn: relativeDomainName=13,zoneName=3.200.10.in-addr.arpa,cn=dns,dc=uni,dc=dtr -relativeDomainName: 12 +relativeDomainName: 13 dn: cn=default-settings,cn=dns,cn=dhcp,cn=policies,dc=uni,dc=dtr -univentionDhcpDomainNameServers: 10.200.3.12 +univentionDhcpDomainNameServers: 10.200.3.13 dn: cn=ox12,cn=dc,cn=computers,dc=uni,dc=dtr -aRecord: 10.200.3.12 +aRecord: 10.200.3.13 +macAddress: 52:54:00:6a:02:1c dn: cn=ucs-local-to-domain,cn=portal,cn=univention,dc=uni,dc=dtr -univentionPortalEntryLink: https://10.200.3.12/univention/portal/ -univentionPortalEntryLink: http://ox12.uni.dtr/univention/portal/ -univentionPortalEntryLink: https://ox12.uni.dtr/univention/portal/ -univentionPortalEntryLink: http://10.200.3.12/univention/portal/ +univentionPortalEntryLink: http://10.200.3.13/univention/portal/ +univentionPortalEntryLink: http://ox12.uni.dtr/univention/portal/ +univentionPortalEntryLink: https://ox12.uni.dtr/univention/portal/ +univentionPortalEntryLink: https://10.200.3.13/univention/portal/
I installed a fresh UCS 5.0 without Samba. When I changed the IPv4 address of the system (m31.uni.dtr, old IP 10.200.3.31, new IP 10.200.3.32) in UCS 5.0, the domain DNS server (itself) as well and the external DNS server from 10.200.3.1 to 192.168.0.124. I got the following pop up: ---------------------------------------------------------------------------- Die folgenden Änderungen werden auf das System übertragen: Domänen-DNS-Server: 10.200.3.32 Externer DNS-Server: 192.168.0.124 Netzwerkgeräte: Verändert: eth0 (Ethernet): Statisch: 10.200.3.32/24 ---------------------------------------------------------------------------- Then the following LDAP entries were changed: ---------------------------------------------------------------------------- None.
The reason nothing is written to LDAP is, can be found by looking at /var/log/univention/setup.log, where the setup-scripts write to: ----------------------------------------------------------------------------- uss.network.plug:Phase skipped: Missing LDAP ----------------------------------------------------------------------------- To check for LDAP availability, the contents of the file /var/run/univention-system-setup.ldap are read. On my system I had used the network UMC module at 12.05.21 12:35:07.114, but the file is older: ----------------------------------------------------------------------------- root@m31:~# ls -la /var/run/univention-system-setup.ldap -rw-r--r-- 1 root root 8 Mai 12 11:43 /var/run/univention-system-setup.ldap ----------------------------------------------------------------------------- root@m31:~# cat /var/run/univention-system-setup.ldap no-ldap ----------------------------------------------------------------------------- The file is created by base/univention-system-setup/usr/lib/univention-system-setup/scripts/setup-join.sh during system-setup, but never cleaned up.
When the file /var/run/univention-system-setup.ldap is removed, the expected LDAP changes are done. This bug will be resolved by fixing bug 51683. Shifting work to that bug.
*** This bug has been marked as a duplicate of bug 51683 ***
OK bug 51683 fixes this
UCS 5.0 has been released: https://docs.software-univention.de/release-notes-5.0-0-en.html https://docs.software-univention.de/release-notes-5.0-0-de.html If this error occurs again, please use "Clone This Bug".