eZDeploy issues
See the following sections for information about troubleshooting issues with the eZDeploy toolkit:
You can check the following log file for entries that might help diagnose the problem:
Log file | Location | Details |
|---|---|---|
eZDeploy.log | eZDeployInstallationDirectory/eZDeploy.log | eZDeploy logs each step in this log file. |
agent.txt | Temp/logs Note: You can find additional log files related to command output at this location. | It logs nsh version. |
ImportBlueprintResponse.json | JSON response after importing the blueprint in BMC CLM. | |
<Software_Package_Name>.txt | Temp/logs/depotid | Details the logs related to folder location in BMC Server Automation for the imported software packages. |
<Software_Package_Name>_error-commandOutput.txt | ||
<Software_Package_Name>_output-commandOutput.txt | ||
<Software_Package_Name>_error-commandOutput.txt | Temp/logs/export | Details the logs related to export of service blueprint, BMC Server Automation artifacts, and BMC Atrium Orchestrator workflows. |
<Software_Package_Name>_output-commandOutput.txt | ||
check_vgp_type_error-commandOutput.txt | Temp/logs/installable | Details the logs related to installable resources or VGP. |
check_vgp_type_output-commandOutput.txt | ||
list_vgp.txt | ||
VGPType.txt | ||
publish_job_error-commandOutput.txt | Temp/logs/publish | Details the logs related to publish product catalog job. |
publish_job_output-commandOutput.txt | ||
publishJob.txt | ||
<NSH Script name>.nsh | Temp/scripts | Contains the NSH scripts used in eZDeploy for import and export operations. |
<Software_Package_Name>.txt | Temp/logs/import | Contains BLCLI import command execution details. It details the error, output, and successful completion of the import of software packages and NSH scripts. |
<Software_Package_Name>_error-commandOutput.txt | ||
<Software_Package_Name>_output-commandOutput.txt | ||
<NSH Script name>.txt | ||
<NSH Script name>_error-commandOutput.txt | ||
<NSH Script name>_output-commandOutput.txt |
No authentication profile found error
The No Authentication Profile Found error appears in the log file. This error often appears if you have deleted the BMC Server Automation Server Authentication Profile by mistake from the BMC Server Automation console.
To work around this issue, you must delete the eZDeploy profile and create it again. See Managing-eZDeploy-profiles for details.
Unable to change the server details
No option is provided for the profile command to change the BMC Server Automation or BMC Atrium Orchestrator servers.
To work around this issue, open the eZDeployInstallationDirectory/profiles directory. You can see .json files with the file name as eZProfileName. Open the file that you want and modify the server details.
Invalid content exported in the eZ file
If you provide an incorrect version of a BMC Atrium Orchestrator activated module for a service blueprint export, the module with invalid content is exported in the eZ file.
To work around this issue, ensure that you provide the correct version of the BMC Atrium Orchestrator activated module when you export a blueprint.
Software packages or deploy jobs missing in the exported eZ file
BMC Server Automation software packages or deploy jobs are not exported in the eZ file.
Ensure that in your BL Packages, the deploy job name and PRODUCT_NAME must be same for eZDeploy to export packages. Failure to do so does not allow eZDeploy to extract the software.