PI95199: STEPS WITH "RUN ON CHANGED RESOURCE" ENABLED INSIDE OF A "FOR EACH TAG" STEP CAN RUN ON RESOURCES THAT WITHOUT THE SPECIFIED TAG

APAR status

• Closed as program error.

Error description

• When we run a "For Each Tag" step we intend that steps only run
  on resources that have, or inherit, a specific tag.
  
  However when the process inside a "For Each Tag" step contains a
  step with "Run If Components Change" enabled, the step will run
  on any resources that have an inventory changed from the
  specified component - regardless of Tag.
  
  Steps to reproduce:
  
  Consider the following resource Tree:
  - Base resource
  --- Blue Resource Group [Blue Tag]
  ------ ComponentA
  ---Green Resource Group [Green Tag]
  ------ ComponentA
  
  And a linear application process that looks like this:
  1) Start
  2) Install Component (runs deploy process for Component A)
  3) For Each Tag step that has the following process inside of
  it:
  ---- 3a) Start
  ---- 3b) Run Operational Process with Run if Components Change
  enabled, and ComponentA specified as the list of Components.
  Keep "only resources where selected components are changed"
  toggled
  ---- 3c) Finish
  4) Finish
  
  Expected Behavior:
  When we run this process we would expect to see ComponentA
  deployed to Base\Blue Group\ComponentA and Base\Green
  Group\Component A, and then the For Each Tag step to iterate on
  the Blue tag, and then the Green Tag.
  
  When the step iterates on the Blue Tag we would expect to see
  that the Operational Process ran on the Base\Blue
  Group\ComponentA resource only (assuming that the inventory for
  Component A has changed on this resource)
  When the step iterates on the Green Tag we would expect to see
  that the Operational Process ran on the Base\Green
  Group\ComponentA resource only
  
  Defect Behavior:
  However we actually see that process is ran on the Base\Blue
  Group\ComponentA and Base\Green Group\ComponentA resources
  during the Blue iteration AND the Green iteration.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When we run a "For Each Tag" step we intend that steps only  *
  * run                                                          *
  * on resources that have, or inherit, a specific tag.          *
  *                                                              *
  * However when the process inside a "For Each Tag" step        *
  * contains a                                                   *
  * step with "Run If Components Change" enabled, the step will  *
  * run                                                          *
  * on any resources that have an inventory changed from the     *
  * specified component - regardless of Tag.                     *
  *                                                              *
  * Steps to reproduce:                                          *
  *                                                              *
  * Consider the following resource Tree:                        *
  * - Base resource                                              *
  * --- Blue Resource Group [Blue Tag]                           *
  * ------ ComponentA                                            *
  * ---Green Resource Group [Green Tag]                          *
  * ------ ComponentA                                            *
  *                                                              *
  * And a linear application process that looks like this:       *
  * 1) Start                                                     *
  * 2) Install Component (runs deploy process for Component A)   *
  * 3) For Each Tag step that has the following process inside   *
  * of                                                           *
  * it:                                                          *
  * ---- 3a) Start                                               *
  * ---- 3b) Run Operational Process with Run if Components      *
  * Change                                                       *
  * enabled, and ComponentA specified as the list of Components. *
  * Keep "only resources where selected components are changed"  *
  * toggled                                                      *
  * ---- 3c) Finish                                              *
  * 4) Finish                                                    *
  *                                                              *
  * Expected Behavior:                                           *
  * When we run this process we would expect to see ComponentA   *
  * deployed to Base\Blue Group\ComponentA and Base\Green        *
  * Group\Component A, and then the For Each Tag step to iterate *
  * on                                                           *
  * the Blue tag, and then the Green Tag.                        *
  *                                                              *
  * When the step iterates on the Blue Tag we would expect to    *
  * see                                                          *
  * that the Operational Process ran on the Base\Blue            *
  * Group\ComponentA resource only (assuming that the inventory  *
  * for                                                          *
  * Component A has changed on this resource)                    *
  * When the step iterates on the Green Tag we would expect to   *
  * see                                                          *
  * that the Operational Process ran on the Base\Green           *
  * Group\ComponentA resource only                               *
  *                                                              *
  * Defect Behavior:                                             *
  * However we actually see that process is ran on the Base\Blue *
  * Group\ComponentA and Base\Green Group\ComponentA resources   *
  * during the Blue iteration AND the Green iteration.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• A fix is available in IBM UrbanCode Deploy 7.0.0.1
  

Temporary fix

Comments

APAR Information

• 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