On 24. 9. 2021, at 9:43, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com> wrote:
BTW: there are two things that are not so clear to me:
1. Is this only impacting SHE environments or is it a general problem also with external
standalone engine ones?
it’s affecting all VMs, in standalone envs engine is not a VM
2. Is it correct to say that if I already upgraded in the past to
4.4.7 and at that time I updated my cluster level from 4.5 to 4.6 (both in case of SHE and
external engine), then I shouldn't have this kind of problems if then I updated to the
impacted 4.4.8-5 version? And then I can go and continue updating to 4.4.8-6 without any
risk/problems?
the cluster level update problem is just a side effect of the time zone missing. You will
see problems in other flows, or next time you upgrade to 4.7 if we ever have one.
Thanks,
Gianluca
On Thu, Sep 23, 2021 at 9:45 PM Diggy Mc <d03(a)bornfree.org
<mailto:d03@bornfree.org>> wrote:
The only VM that my cluster compatibility upgrade complains about is
"HostedEngine". I'm not about to test my SQL knowledge by writing my own
SQL command and I see no reason to touch VMs that don't upset the cluster upgrade.
Can you please provide a SQL command that corrects ONLY the HostedEngine VM ??? Much
appreciated. NOTE: All my servers' OS (physical and VM) are set to
"Etc/UCT" wherever possible.
update vm_static SET time_zone='Etc/GMT' where vm_name='HostedEngine';