IBM Support

PI61809: YOU MAY BECOME UNABLE TO DELETE A RESOURCE TEMPLATE

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

  • Steps to reproduce with two servers
    
    On Source:
    
    1. Create an application A (not from template) with an
    environment
    E1 and a component C
    
    2. Add a Top Resource T , an Agent and the component C to
    the
    Environment E1
    
    3. Create a Resource template X from the resource T. It
    contained
    the agent and the Component under the agent
    
    4. Create an Application Template B with an Environment
    template B1,
    based on the above Resource template X
    
    5. Export the Application Template B and the Application A
    
    On Target:
    
    1. Import the Application A, this created the Component C
    with
    empty environment E1
    
    2. Import the Application Template B. This created the
    Resource
    Template X
    
    Important: in the Resource Template, the Agent appeared as a
    regular
    folder, not like an Agent, but there was no error.
    
    3. Open the environment E1 of the Application A, added a Top
    resource
    
    4. Select: Add from template
    
    and then selected the template X:
    
    Cannot add a component at /top/X/IBM277-R90FKAU9/C because it
    does not
    have an ancestor agent.
    
    where
    IBM277-R90FKAU9
    is the name of my original agent available on the source server
    (no
    agent was so far available on the target server).
    
    (So far so good)
    
    Now when you delete things so that I can redo the import after I
    attached the agent to target server.
    
    1. Delete the Application template B. This will take care of
    deleting the Environment template B1
    
    2. Delete the Application A: Assume that this will take care
    of deleting the Environment E1
    
    3. Delete the Resource Template X: it fails with the message:
    Cannot delete a resource template that is in use by an
    environment template. Used by: 'B1'
    
    When you check the Derby database:
    
    DS_RESOURCE_TEMPLATE contains X but no B1
    
    SEC_RESOURCE still contains B1 as Enabled. I set Enabled to N as
    follows:
    
    ID                                       VERSION     NAME
    ENABLED     SEC_RESOURCE_TYPE_ID
    ------------------------------------     -------
    -----------------     -------
    --------------------------------
    aa8a78b5-866c-4066-966a-cd15d0ae57cc          0    B1
    N          20000000000000000000000000000113
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All environments and users.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Resource templates that included an Agent instead of Agent   *
    * Prototype were causing resource templates to import          *
    * incorrectly.                                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fix provided in UCD 7.0.4.0. Agents are now able to be added to
    resource templates and can be imported / exported successfully.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI61809

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    620

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-03

  • Closed date

    2019-10-30

  • Last modified date

    2019-10-30

  • 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

[{"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":"620","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
30 October 2019