Skip to Content
Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Deploy Job failed - Scenario 1

Error Message

[rpm-version.arch]: Caching enabled but no local cache of //<staging>/blrepos/repo/packages/[rpm-version.arch].rpm from repo

Description

Prior to installing the packages, the Deploy Job runs a preliminary yum analysis. During this analysis scan, rpm-version.arch is found as missing. The Deploy Job does not find rpm-version.arch in the list of staged missing patches, and, therefore, the job cannot proceed.

An error is logged, alerting you that the patch payload is not found and cannot be installed. This error indicates that a discrepancy was found between the regular Patch Analysis and the preliminary yum scan during Deploy, or that rpm-version.arch was not copied during staging. The error message is written in either the Deploy Job log or the bldeploy log.

Troubleshooting

  1. Review Patch Analysis results and check whether rpm-version.arch was found as missing.
  2. If the file is missing, check whether it was packaged during patch remediation.
    • If it was packaged, check whether it points to an existing source. Open the object from inside the Catalog and review its Installable source value.
      • The root cause of the problem might be that the installable source points to a missing payload. In this case, rerun the Catalog or download the patch manually.
      • If the source points to an available payload, review the stage phase of the Deploy Job. Check for issues that might have occurred during the copying of the payload to the target.
    • If the object was not packaged, check for possible RBAC issues.

  3. If patch was not found missing, compare yum scans of Analysis and Deploy:

    • Analysis: <staging>/LinuxCatalog_XXX_[target]/yum_analysis.res
    • Deploy: <staging>/XXXXX/blres.yum.depl

     

    Warning

    The deploy log exists if the Deploy Job was set to preserve staging area on failure. If not, configure this setting now, then reproduce the error and collect the log file.

  4. Compare the lists of set to be updated patches.
    This comparison might reveal that for some RPMs, the analysis finds one arch file missing, while Deploy finds the other one missing. This might be the cause of the original issue. If so, a fix is available in BMC Server Automation 8.1 Service Pack 3.
  5. If the preceding steps did not reveal the root cause of the issue, collect several logs and contact BMC Support. From the application server, obtain the Patch Analysis Job log. In addition, obtain the following logs from the target:
    • Analysis bundle log
    • bldeploy log
    • <staging>/XXXXX/blres.yum.depl

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Server Automation 8.3