Univention Bugzilla – Bug 30286
image creation fails due to lost DNS ability
Last modified: 2014-06-12 09:19:41 CEST
on a memberserver the imagecreation fails with following error:
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
stop: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
Started "/usr/sbin/ucc-image -C -t /var/lib/univention-client-boot -c ucc-default-thinclient.cfg" at 2013-02-05 15:38:04
The command "/usr/sbin/chroot /tmp/tmpdrOoh3/bootstrap apt-get --no-install-recommends install --yes --force-yes xserver-xorg-input-mouse" failed with the error code 100
Traceback (most recent call last):
File "/usr/sbin/ucc-image", line 314, in <module>
File "/usr/sbin/ucc-image", line 59, in _run_cmd
RuntimeError: The command "/usr/sbin/chroot /tmp/tmpdrOoh3/bootstrap apt-get --no-install-recommends install --yes --force-yes xserver-xorg-input-mouse" failed with the error code 100
The former resolveable repositoryserver is not resolvable anymore at some point.
Full Log attached.
The same behaviour also occurs on a DC Slave.
After checking all DNS settings it appears to only occur if no DNS forwarder is set.
ucr set dns/forwarder1=$(ucr get nameserver1)
tested on DC Slave and memberserver with univention-bind installed.
We will document the workaround in the manual.
In UCC 1 the buildserver resolv.conf was copied to the bootstrap directory. It gets overwritten during univention config registry installation. On a memberserver, DNS does then not work in the bootstrap-chroot.
The fix for ucc-image sets the ucr variable nameserver1 in the bootstrap environment during the image bootstrap.
r50152 ucc-image-toolkit 2.0.7-1.188.201405121353
Ok, I could successfully built a thin client image on UCC member server.
UCC 2.0 has been released:
If this error occurs again, please use "Clone This Bug".