The KB that was out on this was a little misleading and seemed out of date for 5.1 so I wanted to share my experiences this morning in attempts to save others that are facing this issue a little time. Apologies if this seems redundant and unnecessary since there is a KB already, this is more of a spoon feeding approach.
Unable to start vApp "vApp Name". Unable to create deployment package. Failed to execute process [/opt/vmware/vcloud-director/deploymentPackageCreator/deploymentPackageCreator]. Standard Output: Standard Error: DeployPkgError exception: error creating archive.
When attempting to run deploymentPackageCreator in /opt/vmware/vcloud-director/deploymentPackageCreator/ manually I kept getting errors stating:
error while loading shared libraries: libCreatePkg.so: cannot open shared object file: No such file or directory.
I used the first command in the KB to export the library that deploymentPackageCreator was complaining about but used the 5.1 name of the vcloud-director directory.
exportLD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/vmware/vcloud-director/deploymentPackageCreator
I verified this by going back and attempting to run deploymentPackageCreator again, and this time I received a much more positive result of deploymentPackageCreator asking for proper usage to run the command.
Usage: ./deploymentPackageCreator <sourcedirpath> <packagepath> <startupcommand> <includesubdirsflag>
Where
sourcedirpath=Fully qualified path to the directory containing the files to be packaged in the deployment package.
packagepath=Fully qualified path to the deployment package file.
startupcommand=Startup command for the deployment package
includesubdirsflag=1/0 (flag specifying whether to include sub directories under sourcedirpath)
Again I followed the KB information which tells you to run a series of commands, which didn't work. However they point you to another series of commands that need to be tweaked for 5.1 usage.
/opt/vmware/vcloud-director/deploymentPackageCreator/deploymentPackageCreator /opt/vmware/vcloud-director/guestcustomization/unix /opt/vmware/vcloud-director/guestcustomization/unix_deployment_package.tar.gz "/bin/sh /tmp/.vmware/linux/deploy/customize-guest.sh start" 0
Finally the KB has you run a command to unset the library.
unsetLD_LIBRARY_PATH
I ran the last two steps in reverse order, but I don't think it matters much.