I recently upgraded all our standalone VRO instances from 7.2.1 to 7.5.0 (which is actually a migration really, rather than an upgrade), and all was well.
Well it was until a few weeks later when one of the flows stopped working with a permissions error. It was a flow that doesn’t get used often, and involved building a file in /tmp on the Orchestrator node, then copying it to the target VM.
Part of our upgrade instructions included adding +rwx /tmp/ to the end of the /etc/vco/app-server/js-io-rights.conf file to permit this, and I was surprised to see it wasn’t there. I chalked this down to human error, but when it happened again on another node, I suspected it was getting overwritten.
A support call quickly determined that there is a new process (which isn’t mentioned in the 7.5 install guide) for manually updating these files:
- Stop the VRO Control Center
service vco-configurator stop - Make manual changes
- Execute
/var/lib/vco/tools/configuration-cli/bin/vro-configure.sh sync-local
Warning: This restarts the VRO service (vco-server) - Start the VRO Control Center
service vco-configurator start
The appliance can then be rebooted without losing the changes to the file(s).
(this is also mentioned in the vmware communities
https://communities.vmware.com/message/2772867#2772867 )
YAVB - Rich Dowling 