Univention Bugzilla – Bug 38275
Make the nameserver and domain setting transparent in the appliance wizard
Last modified: 2015-11-17 12:12:07 CET
Currently, it is a little bit complicated if a docker container should be configured. The hostname is fixed and can't be changed. Thus, the domainname can't configured during the setup. After selecting "Create a new UCS domain" or "Join into an existing UCS domain" or "Join into an existing Active Directory domain" a extra docker page should be shown: - The hostname is shown grayed which a note that it can only be changed while creating the instance - The domainname is set to the UCR domainname setting but the value should be changeable - The nameserver setting is set to the UCR value for nameserver1 and nameserver2 and it should be changeable as well
On a master it looks good. On a slave it doesn't work. I've started a docker container in this way: docker run -d --name=slave --hostname=slave -e domainname=test.local -e rootpwd=univention -p 8081:80 univention/slave-ucs-4.0-1-update-amd64 /sbin/init I was able to set the DNS server in system setup but it didn't find the SRV record of the master. I disabled the automatic search of the master via DNS and typed the FQDN of the master directly. It got further but later the setup failed.
Merged from the original ucs-container scope: univention-system-setup 9.0.2-2.916.201509180943 Did not test it again, though
The change in svn r63832 broke the validation of interfaces. A empty definition of interfaces is send in the setup/validate call which causes that it's not possible to continue when doing a new UCS 4.1 installation. - if (this.isPageVisible('network')) { + if (this.areFieldsVisible('network')) {
Fixed in univention-system-setup 9.0.2-3.917.201510011535
Normal UCS installation: OK UCS Appliance: OK Docker Setup Master: OK Docker Setup Slave: OK Changlog: OK
UCS 4.1 has been released: https://docs.software-univention.de/release-notes-4.1-0-en.html https://docs.software-univention.de/release-notes-4.1-0-de.html If this error occurs again, please use "Clone This Bug".