Univention Bugzilla – Bug 30994
Too vague error message "Error: The UCC image was not found."
Last modified: 2014-06-12 09:20:01 CEST
If the selected UCC image for installation was not found on the server, the booting client shows the message: "Error: The UCC image was not found."
This message could be more clear:
* Where is the system looking for the image (on server/on client)?
* Filename of the image
* Hint what to check next
A better message could be:
Error: The selected UCC image <Filename> was not found on the server. Please make sure you have downloaded/placed the image correctly like described in <http://docs.univention.de/ucc-manual-1.0.html#installation:imagemanagement> or <http://docs.univention.de/ucc-manual-1.0.html#imagegen:chapter>
The message now states:
Error: The UCC image assigned to this client (configurable in the UMC computer management module on the 'Images' tab) could not be found in the directory /var/lib/univention-client-boot on the server distributing the UCC images. If you are using an official UCC image you need to download the image using the UCC image management module in the UMC. If a locally customised image is to be used, it needs to be copied to /var/lib/univention-client-boot.
We could show exactly where the ucc client is looking for the image: the cmdline parameter nfsroot holds the information.
The lines are too long and are wrapped.
Plymouth only shows the last "notice" we send: So while plymouth is running, only the line "If a locally customised image is to be used, it needs to be copied to /var/lib/univention-client-boot." is shown, and even that is wrapped in my test.
-> We should think about stopping plymouth when showing extensive error messages.
Plymouth is now disabled before displaying the error message.
I've also reformulated the error message to include $nfsroot.
OK: Plymouth is disabled, $nfsroot is printed in the error message
UCC 2.0 has been released:
If this error occurs again, please use "Clone This Bug".