IBM Support

PI45398: CHANGING RESOURCE PARENT DOES NOT CHANGE INHERITED TEAMS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Reproduction steps:
    
    1.) Map a resource (resource A) in your resource tree.
    2.) Configure your resource to inherit teams (team A) from
    parent resource
    3.) Configure another resource to have a different set of team
    (team B) mappings
    4.) Click and drag the first resouce (resource A) to be a child
    of the second resource (resource B)
    5.) Note that the child resource (resource A) did not then
    inherit its team mapping from the parent resource (resource B)
    
    Expected results:
    
    The resource would inherit the teams of the new parent and no
    longer inherit the teams of the previous parent.
    
    Actual result:
    
    The resource still has the same teams from the previous parent
    resource.
    

Local fix

  • Workaround: Go into the resource configuration, uncheck Inherit
    Teams From Parent, save, go back to configuration, check Inherit
    Teams From Parent, and save again.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Reproduction steps:                                          *
    *                                                              *
    * 1.) Map a resource (resource A) in your resource tree.       *
    * 2.) Configure your resource to inherit teams (team A) from   *
    * parent resource                                              *
    * 3.) Configure another resource to have a different set of    *
    * team                                                         *
    * (team B) mappings                                            *
    * 4.) Click and drag the first resouce (resource A) to be a    *
    * child                                                        *
    * of the second resource (resource B)                          *
    * 5.) Note that the child resource (resource A) did not then   *
    * inherit its team mapping from the parent resource (resource  *
    * B)                                                           *
    *                                                              *
    * Expected results:                                            *
    *                                                              *
    * The resource would inherit the teams of the new parent and   *
    * no                                                           *
    * longer inherit the teams of the previous parent.             *
    *                                                              *
    * Actual result:                                               *
    *                                                              *
    * The resource still has the same teams from the previous      *
    * parent                                                       *
    * resource.                                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to UCD version 6.2.0.0                               *
    ****************************************************************
    

Problem conclusion

  • Fixed in UCD version 6.2.0.0
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI45398

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    611

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-07-21

  • Closed date

    2015-10-29

  • Last modified date

    2015-10-29

  • 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

  • R600 PSN

       UP

  • R600 PSY

       UP

  • R601 PSN

       UP

  • R601 PSY

       UP

  • R610 PSN

       UP

  • R610 PSY

       UP

  • R611 PSN

       UP

  • R611 PSY

       UP

  • R612 PSN

       UP

  • R612 PSY

       UP

  • R613 PSN

       UP

  • R613 PSY

       UP

  • R620 PSN

       UP

  • R620 PSY

       UP

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

Document Information

Modified date:
17 October 2021