deploy.sh script fails to execute on Aria Automation Orchestrator with "error parsing STDIN"

Products

• VCF Automation

Issue/Introduction

• Standalone Aria Automation Orchestrator service fails to initialize. 
• The /opt/scripts/deploy.sh script fails to execute and bring the services up. 
• The /var/log/deploy.log show the appy_profile.sh sub script failing out to read data from the custom profile yaml indicating file corruption:
  + /opt/scripts/apply_profiles.sh
Profile custom-profile: enabled
error: error parsing STDIN: error converting YAML to JSON: yaml: control characters are not allowed
Profile custom-profile: failed to apply helm overrides

Environment

• Aria Automation Orchestrator 8.x

Cause

• The deploy.sh fails to read data from the corrupted custom profile file and thus errors out. 
• This could be caused due to:
  • Incorrect permissions on the 90-resoruces.yaml file.
  • Missing EOF character on the file.
  • Incorrect formatting of the file contents

Resolution

• Review the custom profiles on "/etc/vmware-prelude/profiles/custom-profile/helm/prelude_vco/90-resources.yaml and make a note of any custom configuration values, which would need to be replaced into the new file. Do not override/modify/delete any existing configuration when recreating the custom profile.
  • cd /etc/vmware-prelude/profiles/custom-profile/helm/prelude_vco/
  • ls -ltrh 90-resources.yaml
  • cat 90-resources.yaml
• Backup the existing 90-resources.yaml file:
  • mv 90-resources.yaml 90-resources.yaml.bkp
• You can create a new custom profile file and populate values with the required configurations as earlier in the 90.resources.yaml.bkp as per KB372697
• Ensure the file permissions on 90-resoruces.yaml is 644
  • chmod 644 90-resources.yaml
• Once done, re run the deploy.sh script and monitor the execution and the pods status
  • /opt/scripts/deploy.sh