Service broker requests with manual user interactions time out after 10,080 minutes

Products

• VMware Aria Suite

Issue/Introduction

This article describes how to increase the hardcoded default 7-day timeout for Service broker requests leveraging manual user interactions.

Symptoms:

• Service broker requests with manual user interactions timeout after 10,080 minutes (7days) despite a greater timeout value being specified at the project level. The request fails in the UI with:

Request timed out after 10,080 minutes. Please configure project request timeout parameter for long running resource requests.

Environment

VMware Aria Automation 8.x

Cause

Service broker requests with manual user interactions have a hardcoded timeout of 7 days.

Resolution

Procedure: Increase the timeout value

1. SSH into the VMware Aria Automation (formerly vRealize Automation) 8.x appliance and run the command as root user.
2. Create the custom profile directory and the required directory tree that is used when the profile is active by running the following script:

   vracli cluster exec – bash -c 'base64 -d <<< IyBDcmVhdGUgY3VzdG9tIHByb2ZpbGUgZGlyZWN0b3J5Cm1rZGlyIC1wIC9ldGMvdm13YXJlLXByZWx1ZGUvcHJvZmlsZXMvY3VzdG9tLXByb2ZpbGUvCgojIENyZWF0ZSB0aGUgcmVxdWlyZWQgZGlyZWN0b3J5IHRyZWUgdGhhdCB3aWxsIGJlIHVzZWQgd2hlbiB0aGUgcHJvZmlsZSBpcyBhY3RpdmUKbWtkaXIgLXAgL2V0Yy92bXdhcmUtcHJlbHVkZS9wcm9maWxlcy9jdXN0b20tcHJvZmlsZS9oZWxtL3ByZWx1ZGUvCgojIENyZWF0ZSAiY2hlY2siIGZpbGUgdGhhdCBpcyBhbiBleGVjdXRhYmxlIGZpbGUgcnVuIGJ5IGRlcGxveSBzY3JpcHQKY2F0IDw8RU9GID4gL2V0Yy92bXdhcmUtcHJlbHVkZS9wcm9maWxlcy9jdXN0b20tcHJvZmlsZS9jaGVjawojIS9iaW4vYmFzaApleGl0IDAKRU9GCmNobW9kIDc1NSAvZXRjL3Ztd2FyZS1wcmVsdWRlL3Byb2ZpbGVzL2N1c3RvbS1wcm9maWxlL2NoZWNrCgojIENvcHkgZGVmYXVsdCB1c2VyIGludGVyYWN0aW9uIHRpbWVvdXQgc2V0dGluZ3MgdG8geW91ciBjdXN0b20gcHJvZmlsZQpjYXQgPDxFT0YgPiAvZXRjL3Ztd2FyZS1wcmVsdWRlL3Byb2ZpbGVzL2N1c3RvbS1wcm9maWxlL2hlbG0vcHJlbHVkZS81MC11c2VyLWludGVyYWN0aW9uLXRpbWVvdXQueWFtbApqYXZhT3B0czoKICAiYmx1ZXByaW50LnJlc291cmNlLnVzZXJJbnRlcmFjdGlvblRpbWVvdXREYXlzIjogIjciCkVPRgpjaG1vZCA2NDQgL2V0Yy92bXdhcmUtcHJlbHVkZS9wcm9maWxlcy9jdXN0b20tcHJvZmlsZS9oZWxtL3ByZWx1ZGUvNTAtdXNlci1pbnRlcmFjdGlvbi10aW1lb3V0LnlhbWwK | bash'

3. Edit the Blueprint resource configuration in your custom profile with the user interaction timeout value in days:

   vi /etc/vmware-prelude/profiles/custom-profile/helm/prelude/50-user-interaction-timeout.yaml

4. The 50-user-interaction-timeout.yaml file should contain the following default properties:

   javaOpts:
   "blueprint.resource.userInteractionTimeoutDays": "7"

Where 7 is the number of days after which the timeout of the resource will occur. Amend this value as desired.

5. Save the changes to the resource metrics file and run the deploy.sh script

   /opt/scripts/deploy.sh

You have now changed the timeout of the Blueprint resource User Interaction; the changes should persist restarts and upgrades.