Univention Bugzilla – Bug 30339
UCC update image does not work when choosing a different image file name
Last modified: 2013-03-26 09:14:46 CET
When changing the image file in umc, e.g. from ucc-1.0-desktop to ucc-1.1-desktop, and changing the setting to update/first installation, the ucc system will start up and detect the rollout mode. It does however not download and install the new image, although the md5sums of the local and remote image differ. The old image name is available in /ucc_root/local_image. Its md5sum in /ucc_root/local_image.md5
We need to fix this to ensure proper updates to 1.1
I've tried to reproduce this issue without success. I installed UCC 1.0 RC via app center and configured a UCC client with the default thin client image. The default image was installed on the client. After that I set the version for the thin client image to 1.1 in /usr/share/doc/ucc-image-toolkit/example/ucc-thinclient.cfg and changed the packages in the file. The new thin client image (1.1) was created with ucc-image: ucc-image -t /var/lib/univention-client-boot -c /usr/share/doc/ucc-image-toolkit/example/ucc-thinclient.cfg ucc-1.1-thinclient-image.img.inst created the new objects and i changed the image for the client to ucc-1.1-thinclient-image.img and set the boot variant to "Image boot with update check / Initial installation". During the next reboot the new image was downloaded and installed. Could you add some debug output?
I can reproduce it, if I use the desktop image and a boot from the local device.
The resolv.conf of the iso image doesn't contain a valid nameserver, so the UCC system can't read the boot flags.
Setting the ucr variables nameserver{1,2,3} to be persistent solves the problem. This was already done in bug 30313.
UCC 1.0 has been released: http://forum.univention.de/viewtopic.php?f=26&t=2417 http://forum.univention.de/viewtopic.php?f=54&t=2418 If this error occurs again, please use "Clone This Bug".