This issue is fixed in vRealize Automation 8.8 and vRealize Automation Cloud.
Workaround:
Prerequisites
- Please take simultaneous non-memory snapshots of each virtual appliance(s) in the cluster.
- You have access to root user and password
- You have SSH or console access to each virtual appliance.
- Download the Docker image titled relocation-service.tar from the Attachment(s) section of this article.
SHA256SUM
5699EEC1F0E09D1AF9B1296DFB1D2D804D70F2856488ED7BE8B08CD32671DA04
Procedure
Perform Steps # 1 - 5 on each appliance
Note: Replace the existing relocation-service with the new image for the fix.
- Upload the Docker image relocation-service.tar to each virtual appliance within the vRealize Automaton cluster.
scp /path/to/relocation-service.tar root@<FQDN>:/
- SSH / PuTTy into the vRealize Automation appliance
ssh root@<FQDN>
- Load the Relocation service image into the local Docker repository
docker load -i relocation-service.tar
- Backup the original image
- Look for the image that is currently tagged with relocation-service_private:latest and note its unique identifier (hash)
docker images | grep -i relocation-service
- Backup the original image
docker tag original-image-id relocation-webapp_backup:latest
- Tag the Relocation service image
docker tag a4eff812ec38 relocation-service_private:latest
- Run the following once on any node
- Apply the patch by restarting the relocation service
kubectl -n prelude scale deployment relocation-service-app --replicas=0
-
For clustered environments use the parameter --replicas=3 and --replicas=1 for simple environments
kubectl -n prelude scale deployment relocation-service-app --replicas=3
Rollback Procedure to restore the original service image
Perform Steps # 1 - 2 on each appliance
- Find the original relocation-service image
docker images | grep -i relocation-webapp_backup:latest
- Re-tag the old image
docker tag original-image-id relocation-service_private:latest
- Run the following once on any node
kubectl -n prelude scale deployment relocation-service-app --replicas=0
- For clustered environments use the parameter --replicas=3 and --replicas=1 for simple environments
kubectl -n prelude scale deployment relocation-service-app --replicas=3