Earlier this year I was working with an IBM Cloud Pak System client who was facing issues with the execution of Script Packages. The client had been creating their own customized Virtual System Patterns with a number of Script Packages that they had created themselves. For reasons we did not understand, some (but not all) Script Packages were failing to run when manually executed after deployment of the Virtual System Pattern.
I reviewed the trace.log of the maestro agent on a VM of the deployed Virtual System Instance, this file can be found in /opt/IBM/maestro/agent/usr/servers/<node_name>/logs/<node_name>/<script-package-name>-Script/trace.log. Here I noticed the following DEBUG message:ScriptUtils.py <id> pid=<pid> DEBUG No value found for attribute key: LOGSERVER_HOSTNAME, returning empty string.
While working through this issue with IBM Support, we found that this issue was caused by special characters in Script Package name. We were using names that contained a colon (:) character, which clashes with the internals of IBM Cloud Pak System. IBM Support confirmed that this issue will be resolved through delivery of APAR IT31777 in a future firmware version for IBM Cloud Pak System. But in the meantime, avoid using colon (:) characters in the name of your Script Packages!
IBM Cloud Pak System 