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 2

Error Message

package [rpm-version] is already installed

 

Description

The Deploy Job installs the patches that were found missing during Analysis. In this case, the Analysis Job packaged the rpm-version, even though it is already installed.

Troubleshooting

  1. Review the Analysis logs to troubleshoot the issue. 

    The error message is located in either the Deploy Job log or the bldeploy log.
    You might see the following log records:

    • The analysis_log.log is expected to reveal that the Patch Analysis ran with an include filter. The signs for this are:
      • After 'update' you see a list of RPMs.
      • YUM Command: for i in 0 1 2 3 4 5 :; do echo n; done | blyum -c ./yum.conf -C update "rpm-version.arch" "…" ...
    • Command rpm –q [rpm] reveals that multiple versions of the rpm are installed.
  2. The expected findings described in the previous step are not the standard configuration. Therefore, perform the following further testing:
    • Run yum update with include list.
      This is expected to produce the following error:latest rpm as missing [issue reproduced]
      The updated rpm is offered for the older version of RPM that is installed even if the new version is also already installed.
    • Run yum update without include list.
      This should return the following message:no missing rpm [good result]
      If we do not forcefully analyze for patches (with an include filter), then if the latest version is found, the rpm is not offered.
    • Run yum install with include list.
      This should return the following message:no missing rpm [good result]
      The Install option checks only for the specific version of the rpm that we are attempting to install. Since our specific version of rpm is already installed, it will not be installed again.
  3. If you must preserve multiple versions of such RPMs, create a separate analysis job where you would use Install option and include the RPM.
  4. Modify the existing Analysis Job include filter and remove the RPM.
    If the RPM must be included, try excluding the opposite set of RPMs. For example, exclude all where RPM does not equal [rpm-version].
  5. Yum does not install multiple versions of such RPMs by default, so if they are not required, then uninstall the old versions.
    The Analysis Job should no longer report the latest RPM as missing, because there will no longer be multiple versions.

Logs to collect

Log files to collect from the application server

  • Patch Analysis Job log

Log files to collect from the target

  • analysis bundle log
  • bldeploy log
  • <staging>/XXXXX/blres.yum.depl
  • rpm –q [rpm]

 

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

BMC Server Automation 8.3