Specific (Optional or Provoked) Task deployment from Packages fail
book
Article ID: 84574
calendar_today
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
Error Message : No error message displayed on UVC console nor in the universe.log file.
Product version Dollar Universe 6.3.41 or higher
When a template task that includes an optional task is deployed from a package to a MU enabling the template to become non-template, the optional task is not included in the deployment.
No error message is displayed. For a better explanation, see screens below:
When package is deployed to a node
When package is deployed to a MU.
Environment
OS: All
Cause
Cause type: Configuration Root Cause: Package is deployed from a different node than the reference node.
Resolution
Solution 1)
The package should be deployed from the reference node so the different MU's targeted used in the optional task can be deployed with the package and created in the new node.
If the package is deployed from a node where the optional task MU does not exist, the optional task won't be deployed.
Solution 2)
From a different node than the reference, create all the MU's required in the package previous the deployment
or
Deploy to the new node first then deploy to a particular MU.