Resolving VMware vRealize Orchestrator DST Issues with a Custom Script
One of my customers encountered issues with VMware vRealize Orchestrator (vRO) after the Daylight Saving Time (DST) transition. Scheduled workflows failed or were triggered incorrectly, disrupting their automated processes. The root cause was incorrect system time zone settings after the DST change. The Solution: To fix the issue, we created a custom VMware Prelude profile using a script that: Created the necessary directories for custom profiles. Added a check script to validate system time zone settings. Ensured proper Helm chart configuration for correct time handling. 1. 1. 1. Please use the following java property in the section serverJavaOpts : "user.timezone":"Australia/Victoria". This time zone Australia/Victoria corresponds to AEST-10AEDT according to https://en.wikipedia.org/wiki/Time_in_Australia With the above applied, ...