PI76883: DEPLOYMENT CAN NOT BE STARTED DUE TO FAILED GATES EVEN IF ALL THE VERSIONS SEEM TO BE PASSING THE GATES

APAR status

• Closed as program error.

Error description

• Some deployments can not be started due to some versions not
  passing the gates. Even if the UI is showing that
  all the versions are passing the gates, it is possible that an
  application that was previously scheduled to be deployed for
  this release would have been removed from the release before the
  deployment starts.
  Even if that application is not showing on the content tab of
  the deployment anymore, it was still be used to calculate if the
  the gates are passing or not. If for some reasons the version
  for that removed application would not pass the gates it would
  cause the gates to fail for that deployment since it used to
  keep a reference to it.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Some deployments can not be started due to some versions not *
  * passing the gates. Even if the UI is showing that            *
  * all the versions are passing the gates, it is possible that  *
  * an                                                           *
  * application that was previously scheduled to be deployed for *
  * this release would have been removed from the release before *
  * the                                                          *
  * deployment starts.                                           *
  * Even if that application is not showing on the content tab   *
  * of                                                           *
  * the deployment anymore, it was still be used to calculate if *
  * the                                                          *
  * the gates are passing or not. If for some reasons the        *
  * version                                                      *
  * for that removed application would not pass the gates it     *
  * would                                                        *
  * cause the gates to fail for that deployment since it used to *
  * keep a reference to it.                                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• A fix is available in IBM UrbanCode Release 6.2.1.3
  

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 RELEASE

• Fixed component ID

  5725M5500

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

• R620 PSN

     UP

• R620 PSY

     UP

• R621 PSN

     UP

• R621 PSY

     UP

• R622 PSN

     UP

• R622 PSY

     UP