ZZ00234: EVENT-BASED ORCHESTRATION GOES INTO ENDLESS LOOP IF VSYS INSTANCE HAS NO ASSOCIATED PATTERN

2.3.0.1-CSI-ISCO-IF0009
IBM SmartCloud Orchestrator Interim Fix 7 for 2.3.0.1
IBM SmartCloud Orchestrator Interim Fix 6 for 2.3.0.1
IBM SmartCloud Orchestrator Interim Fix 5 for 2.3.0.1
IBM SmartCloud Orchestrator Interim Fix 3 for 2.3.0.1
IBM SmartCloud Orchestrator Interim Fix 4 for 2.3.0.1
IBM SmartCloud Orchestrator Interim Fix 8 for 2.3.0.1

APAR status

• Closed as program error.

Error description

• Scenario to reproduce:
  
  1) Create an event-based orchestration, for event "Before
  virtual
  system instance deletion".
  2) Any simple process that ends successfully will do - I had
  one that
  just logs an entry to BPM log.
  3) Deploy a virtual system instance, then delete the pattern the
  instance was provisioned from.
  4) Delete the instance via IWD
  
  The event based orchestration will be triggered, and repeated
  over and
  over again.
  If the associated process terminates, no loop/repeat can be
  observed.
  If a pattern for the instance still exists, no loop/repeat can
  be
  observed.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:
  All users of SmartCloud Orchestrator 2.3.0.0 or 2.3.0.1
  ****************************************************************
  * PROBLEM DESCRIPTION:
  Event-based orchestration goes into a loop if vSys instance has
  no associated pattern.
  ****************************************************************
  * RECOMMENDATION:
  For permanent resolution apply SmartCloud Orchestrator 2.3.0.1
  iFix 3.
  

Problem conclusion

• The event based orchestration will be triggered, and repeated
  over and over again. If a pattern for the instance still exists,
  no loop/repeat can be observed. This is now fixed, each defined
  orchestration action will only be executed once.
  
  The fix for this APAR will be contained in the following
  maintenance packages:
  | ifix | 2.3.0.1-CSI-ISCO-IF0003 applicable for SmartCloud
  Orchestrator 2.3.0 Fix Pack 1 or SmartCloud Orchestrator
  Enterprise 2.3.0 Fix Pack 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

  SMRTCLOUD ORCHS

• Fixed component ID

  5725H2800

Applicable component levels

• R230 PSY

     UP