Univention Bugzilla – Bug 31174
05univention-bind.inst hangs because link local address is not stored in UCR
Last modified: 2013-11-19 06:43:52 CET
UCS-3.1-1 amd64 Master installation
During setup, no DHCP server was found and a IPv4 Link Local address was chosen by the installer.
The network configuration is not written to the installation_profile and thus not to UCR interfaces/eth0/*.
Because of that the hostname is not written to /etc/hosts.
Because of that the symbolic hostname in /etc/ldap/ldap.conf and UCR ldap/master can't be resolved. (DNS is not yet running; that's what the join script is trying to do)
So /usr/share/univention-admin-tools/univention-dnsedit can't contact the LDAP server and the join stalls.
I've tested an installation of an UCS 3.1-1 amd64 master which was configured via DHCP. The server got a link local address but I was not able to reproduce this behavior.
Could you append the logfiles?
Created attachment 5199 [details]
(In reply to comment #1)
> I've tested an installation of an UCS 3.1-1 amd64 master which was configured
> via DHCP. The server got a link local address
To be clear: DHCP did *NOT* return an address, so the link local address 169.254.x.y/16 generated by the installer was used.
> but I was not able to reproduce this behavior.
Reproduced it on all 6 computers of our training lab and on a VM on xen15, which is available for debugging.
> Could you append the logfiles?
See this attachment.
Created attachment 5200 [details]
Created attachment 5201 [details]
Created attachment 5207 [details]
(In reply to comment #0)
> UCS-3.1-1 amd64 Master installation
> During setup, no DHCP server was found and a IPv4 Link Local address was chosen
> by the installer.
OK, it happens if you press F5 for trying the DHCP server and you got no answer. The link local address will be insert in the IPv4 field but the address is not written to the profile.
If you got an IP via DHCP the network settings will be written to the profile.
The installer should not write the link local address into the IP field if no IP was returned.
We will not ship a UCS 3.1-2 release; the next UCS release will be UCS 3.2.
As such, this bug is moved to the new target milestone.
I could not reproduce the actual problem, but changed the network settings ...
* DHCP query button in the network settings has been removed
* DHCP query is performed when dhcp is selected
* if we get an address, we continue with this address, if not
we continue with a link-local (169.254...) address
Tested the installation of an UCS master with interfaces/eth0/type=dhcp and no valid dhcp offer, installation was successful, join fine and after the boot of the system i had an 169.254... ip address
* static addess installation
* dhcp installation with valid dhcp address
* dhcp installation without a dhcp address (link local)
* profil bases installation with dhcp/static address
> * static addess installation
Worked as expected in various installations.
> * dhcp installation with valid dhcp address
Selecting "DHCP" in the network configuration triggers an immediate DHCP request. An installation of a DC master with such a setup and basic UMC tests were succesful.
> * dhcp installation without a dhcp address (link local)
Selecting "DHCP" in the network configuration on a system with a pulled network cable triggers an immediate DHCP request. This DHCP request naturally fails and an error message is displayed. If one proceeds with F12 a link local address is assigned. An installation of a DC master with such a setup and basic UMC tests were successful.
Tests with Univention Net Installer as still missing.
A profile-based installation with DHCP was also successful.
UCS 3.2 has been released:
If this error occurs again, please use "Clone This Bug".