Bug 32867 - Image Postinst fails without error message or exitcode != 0
Image Postinst fails without error message or exitcode != 0
Status: CLOSED INVALID
Product: Z_Univention Corporate Client (UCC)
Classification: Unclassified
Component: Image management
unspecified
Other Linux
: P5 normal
: UCC 2.0
Assigned To: Felix Botner
Moritz Muehlenhoff
: interim-1
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-15 10:05 CEST by Tim Petersen
Modified: 2014-06-12 09:19 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Petersen univentionstaff 2013-10-15 10:05:19 CEST
As described here http://forum.univention.de/viewtopic.php?f=64&t=2935&p=10202, the postinst of the image packages is not executed with set -e ; that leads to an exit code 0 for postinst even if the subprocess (in this case the image download failed) exits!= 0.

Maybe this was desirable in order to prevent failing installations in cases where dns lookups doesn't work or things like that. Anyway this should be intercepted.
Comment 1 Moritz Muehlenhoff univentionstaff 2013-10-15 10:11:25 CEST
Check for 1.1
Comment 2 Felix Botner univentionstaff 2014-04-07 12:03:15 CEST
This is no longer as relevant as we have an image module in the UMC with UCC 2.0.
Comment 3 Moritz Muehlenhoff univentionstaff 2014-04-07 13:33:13 CEST
UCC 2.0 will introduce an image management module in the Univention Management Console which will take care of the downloads. If the image download is incomplete or failed, a error message will be flagged there.

Aborting the installation in the meta package itself is problematic, since it leads a "corrupted" status in the dpkg package installation database.
Comment 4 Moritz Muehlenhoff univentionstaff 2014-06-12 09:19:39 CEST
UCC 2.0 has been released:
 http://docs.univention.de/release-notes-ucc-2.0.html

If this error occurs again, please use "Clone This Bug".