Reservation policy field in a blueprint component is empty in vRealize Automation 7.x

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:
The reservation policy field of a blueprint component is empty despite being filled earlier.

Environment

VMware vRealize Automation 7.x

Cause

This issue occurs because renaming a reservation policy causes any blueprint component that uses that reservation policy to clear the reservation policy field. Blueprints save fields by name, and not by reference, to keep portability.

Resolution

This is a known issue affecting VMware vRealize Automation 7.x.

Currently, there is no resolution.

Workaround:
To work around this issue, re-add the reservation policy to any blueprint component that uses the reservation policy when changing reservation policy names.