Description Dirk Schnick 2022-06-08 09:26:44 CEST

Long summary or topic, but it describes the problem in short.
In a new installed UCS5@school environment I import a network:

5school-intranet.intranet /  0,01 / 09:03:50 / ✓
root@dc0:~ # cat networkImport.csv 
UCS501	192.168.112.0/24		192.168.112.1	192.168.112.3	192.168.112.3

It does not matter if I define an IP range to use for new devices (third value is left empty in that example) the problem occurs in any case.

If I now create a new computer using the UMC computer module and choose the imported network, an IP is chosen automatically. If I now change this IP the computer will be created with my given IP but the DNS entry still uses the automatically chosen IP.
It looks like the UMC do not read the IP address when creating the DNS entry and dully uses the automatically chosen IP.

You can  recreate this problem easily using an UCS5@school installation with master and at least one slave. I used a fresh UCS5 installation (not updated from UCS4). You need to import at least one network (delimiter is tab) like above with network import script /usr/share/ucs-school-import/scripts/import_networks. Then create a new computer using that network and change the automatically chosen IP to any else. Check the DNS entry of that machine.

You can use my test environment 10.200.36.100 (5school-intranet.intranet yeah I know a stupid domain name) Please give me a hint if you will use it.

The problem do not occur if I create a network manual; it looks like the import of the network is relevant. So I choose import scripts as component.