IBM Support

PI80069: SUCCESSFUL DEPLOYMENT SHOWS NON-COMPLIANT INVENTORY

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • A successful deployment of a new component version will show a
    non-compliant inventory because inventory will say the previous
    version is still installed and is not updated when the
    deployment completed. Manual verification of the target
    environment will show that deployment was correct. Errors may
    not be logged at the time of the deployment. The failure is
    intermittent and may become more frequent over time until the
    UCD servers are restarted.
    
    This issue is often associated with the symptoms of APAR
    PI65742, but is not the same defect.
    

Local fix

  • Restarting the UCD servers will temporarily resolve the problem.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * A successful deployment of a new component version will show *
    * a                                                            *
    * non-compliant inventory because inventory will say the       *
    * previous                                                     *
    * version is still installed and is not updated when the       *
    * deployment completed. Manual verification of the target      *
    * environment will show that deployment was correct. Errors    *
    * may                                                          *
    * not be logged at the time of the deployment. The failure is  *
    * intermittent and may become more frequent over time until    *
    * the                                                          *
    * UCD servers are restarted.                                   *
    *                                                              *
    * This issue is often associated with the symptoms of APAR     *
    * PI65742, but is not the same defect.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to UCD version 6.2.4.1                               *
    ****************************************************************
    

Problem conclusion

  • Fixed in UCD version 6.2.4.1
    

Temporary fix

  • Restarting the UCD servers will temporarily resolve the problem.
    

Comments

APAR Information

  • APAR number

    PI80069

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    601

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-17

  • Closed date

    2017-05-01

  • Last modified date

    2017-05-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

  • R624 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
01 May 2017