The released version count associated to a cloud template sometimes does not track the real number of released versions

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Possible symptoms:

1. Within the Template the number of released versions is different from the Released Versions count in the template version history page.
2. When customer releases a template to Service Broker and it appears in Service Broker. However, it disappears after some time while the template is still in "Released" state.

Environment

Aria Automation 8.x

Aria Automation 9.x

Cause

In race conditions (for example, user tries to release or unrelease the same version of a template multiple times in a short period of time), the release version count could be incorrectly incremented or decremented, hence the count is off.

Resolution

Resolution for Aria Automation 8.x

1. Make sure all versions of the template are unreleased
2. Find the template's UUID, which we name it as TEMPLATE_ID
3. Make sure this blueprint or its catalog items are not being used while applying below steps
4. By executing below cmds after ssh into vRA, so that we connect to blueprint DB
   vracli dev psql tango-blueprint-db
5. Then, run below postgres cmd, by populating the TEMPLATE_ID with the real UUID of template
   UPDATE bp_blueprint SET total_released_versions = 0 WHERE id = '${TEMPLATE_ID}';  

 

Resolution for VCF Automation 9.x

1. Make sure all versions of the template are unreleased
2. Find the template's UUID, which we name it as TEMPLATE_ID
3. Make sure this blueprint or its catalog items are not being used while applying below steps
4. By executing below two cmds after ssh into VCFA, so that we connect to blueprint DB
   kubectl -n prelude exec -it vcfapostgres-0 -n prelude -- bash
psql -U postgres tango_blueprint_db
5. Then, run below postgres cmd, by populating the TEMPLATE_ID with the real UUID of template
   UPDATE bp_blueprint SET total_released_versions = 0 WHERE id = '${TEMPLATE_ID}';