Troubleshooting PostPrepare script failed with exit code 1

Question

i get a 'PostPrepare' script failed with exit code '1' message on one of the bundles, and i think i am missing some obvious thing
it is a simple file bundle, to distribute a pdf printer:
it distributes 2 files:
ADIST.PPD to /usr/share/cups/model
pdf-printer to /usr/lib/cups/backend
(script based upon Cool Solutions: A CUPS PDF Printer for your SUSE Linux Enterprise Desktop
then it should execute a pre-installation script that executes:
Code:
#!/bin/bash
rccups restart
mkdir -p /export/share/pdf
chmod -R 777 /export
lpadmin -p Desktop-PDF -v pdf-writer:/export/share/pdf/ -E -P /usr/share/cups/model/ADIST5.PPD -D "PDF Writer for CUPS" -L "PDF on desktop"
manually placing the files on these locations and executing the script works fine
on the machine i get (device set to log debug and above)
Code:
22 Jul 2010 09:33:00 INFO BundleManager Executing preprepare scripts for PDF printer
22 Jul 2010 09:33:00 DEBUG Progress Is Stopped value: False
22 Jul 2010 09:33:00 INFO WebCache Attempting to retrieve 'https://zlmserver/zenworks-pkgmgt/repo/getBundleFile/3ba56c5bc95bb2874273a7d0cae07d14/8/sled-11-i586/ADIST5.PPD' (try 1)
22 Jul 2010 09:33:01 INFO WebCache Successfully retrieved https://zlmserver/zenworks-pkgmgt/repo/getBundleFile/3ba56c5bc95bb2874273a7d0cae07d14/8/sled-11-i586/ADIST5.PPD
22 Jul 2010 09:33:01 DEBUG Progress Is Stopped value: False
22 Jul 2010 09:33:01 INFO WebCache Attempting to retrieve 'https://zlmserver/zenworks-pkgmgt/repo/getBundleFile/3ba56c5bc95bb2874273a7d0cae07d14/8/sled-11-i586/pdf-writer' (try 1)
22 Jul 2010 09:33:01 INFO WebCache Successfully retrieved https://zlmserver/zenworks-pkgmgt/repo/getBundleFile/3ba56c5bc95bb2874273a7d0cae07d14/8/sled-11-i586/pdf-writer
22 Jul 2010 09:33:01 DEBUG Progress Is Stopped value: False
22 Jul 2010 09:33:01 DEBUG Progress Is Stopped value: False
22 Jul 2010 09:33:01 INFO BundleManager Executing postprepare scripts for PDF printer
22 Jul 2010 09:33:01 DEBUG Progress Is Stopped value: False
22 Jul 2010 09:33:01 INFO BundleManager Successfully prepared bundles
22 Jul 2010 09:33:01 INFO BundleManager Beginning bundle transaction
22 Jul 2010 09:33:01 INFO BundleTransaction Beginning bundle transaction: 1 installs, 0 removals.
22 Jul 2010 09:33:01 INFO BundleTransaction Executing preinstall scripts for PDF printer
22 Jul 2010 09:33:01 INFO SystemCatalog Saving system catalog containing 9 bundles
22 Jul 2010 09:33:01 ERROR BundleTransaction Novell.Zenworks.Zmd.BUNDLE_INSTALL_ERROR: Novell.Zenworks.Zmd.BUNDLE_INSTALL_ERROR
Novell.Zenworks.Zmd.Public.ZenException: 'PreInstall' script failed with exit code '1'
22 Jul 2010 09:33:01 INFO Progress Progress.Stop Message: Bundle transaction failed: 'PreInstall' script failed with exit code '1'
22 Jul 2010 09:33:01 DEBUG Progress Is Stopped value: False
22 Jul 2010 09:33:01 ERROR BundleManager Transaction failed: Bundle transaction failed: 'PreInstall' script failed with exit code '1'
22 Jul 2010 09:33:01 INFO Progress Progress.Stop Message: Parent failed/aborted
22 Jul 2010 09:33:01 DEBUG Progress Is Stopped value: False
22 Jul 2010 09:33:01 INFO Progress Progress.Stop Message: Parent failed/aborted
22 Jul 2010 09:33:01 DEBUG Progress Is Stopped value: False
22 Jul 2010 09:33:01 INFO Progress Progress.Stop Message: Parent failed/aborted
22 Jul 2010 09:33:01 DEBUG Progress Is Stopped value: False
22 Jul 2010 09:33:01 INFO Progress Progress.Stop Message: Parent failed/aborted
22 Jul 2010 09:33:01 DEBUG Progress Is Stopped value: False
22 Jul 2010 09:33:01 ERROR ActionManager Failed to execute scheduled action (install (bundles=3ba56c5bc95bb2874273a7d0cae07d14)): Bundle transaction failed: Bundle transaction failed: 'PreInstall' script failed with exit code '1'
Novell.Zenworks.Zmd.Public.ZenException: Bundle transaction failed: Bundle transaction failed: 'PreInstall' script failed with exit code '1'
22 Jul 2010 09:33:01 INFO BundleTransaction Bundle transaction ended.
clients: sled11sp1 i586
server: sles11 x64 + zlm732
the files are not copied to their destination
the target directories are available, writable by root (obviously) there are no files with the same name available, adding a trailing slash to the target path does not help (but other bundles have no trailing slash and run ok)
questions:
where are the temporary files copied to?
where/how can i find what might be causing the preinstall error?
should i delete previous versions of the bundle in zlm

Answer 1

until you delete the previous version in zlm and do a rug ref... or is this as designed
When you make changes to the bundle you need to apply them. That creates a new version and then you need to deploy that new version. Apply and deploy are on the same page. But I guess you know that.
If you already did that and still had problems, it might be the zen loader that needs a little bit more time. Once you hit deploy, a zen queue entry gets created that informs the zen loader to update the bundle xml file in the file repository. That file is delivered to the managed device when it queries for bundle information. So if that bundle xml contains the old version, the client will see that.
Problems here can be that the zen loader simply needs a few seconds longer then when you change to the device and run rug ref. Or there can be other queue entries that get processed and the bundle xml update is just in the queue and waiting. The zen loader has 5 slots for processing queue entries.
On the zlm server you can run "zlman ql I" for in progress entries and "zlman ql N" for new state entries that ned to be processed.
Or you can use the short script I posted (Cool Solutions: Monitor ZLM queue entries with Nagios) that shows you in one line how many and what type of queue entries currently exist. This is what I always use to get a overview about the queue status.
Rainer