Dear all, I have just updated my ovirt installation, with self hosted engine, from 4.4.5 to 4.4.8.5-1. Everything went smoothly and in a few minutes the system was back up and running. A little issue is still puzzling me. I am asked to update from 4.5 to 4.6 the cluster and data center compatibility level. When I try to issue the command from the cluster config I get this error:
Error while executing action: Cannot update cluster because the update triggered update of the VMs/Templates and it failed for the following: HostedEngine. To fix the issue, please go to each of them, edit, change the Custom Compatibility Version (or other fields changed previously in the cluster dialog) and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change (or other changes). If the problem still persists, you may refer to the engine.log file for further details.
It's very strange because the config of the hostedengine is "plain" and there are no constrains on compatibility version, as you can see in this picture: In any case, if I try to force compatibility with 4.6 I get this error:
Error while executing action:
HostedEngine:
There was an attempt to change Hosted Engine VM values that are locked.
So I am stuck. Not a big deal at the moment, but sooner or later I will have to do this upgrade and I don't know where I am wrong. Can anybody give a clue? Thanks in advance, Andrea -- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz --
Really no suggestions at all? Andrea On 15/09/2021 12:33, Andrea Chierici wrote:
Dear all, I have just updated my ovirt installation, with self hosted engine, from 4.4.5 to 4.4.8.5-1. Everything went smoothly and in a few minutes the system was back up and running. A little issue is still puzzling me. I am asked to update from 4.5 to 4.6 the cluster and data center compatibility level. When I try to issue the command from the cluster config I get this error:
Error while executing action: Cannot update cluster because the update triggered update of the VMs/Templates and it failed for the following: HostedEngine. To fix the issue, please go to each of them, edit, change the Custom Compatibility Version (or other fields changed previously in the cluster dialog) and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change (or other changes). If the problem still persists, you may refer to the engine.log file for further details.
It's very strange because the config of the hostedengine is "plain" and there are no constrains on compatibility version, as you can see in this picture:
In any case, if I try to force compatibility with 4.6 I get this error:
Error while executing action:
HostedEngine:
There was an attempt to change Hosted Engine VM values that are locked.
So I am stuck. Not a big deal at the moment, but sooner or later I will have to do this upgrade and I don't know where I am wrong.
Can anybody give a clue? Thanks in advance,
Andrea
-- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz --
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/BQMHMKNLPANYOI...
-- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz --
Have you tried the windows fix (a.k.a Engine restart )? Best Regards,Strahil Nikolov On Fri, Sep 17, 2021 at 16:43, Andrea Chierici<andrea.chierici@cnaf.infn.it> wrote: _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/2WDJEQYIDZNNIK...
please check bug https://bugzilla.redhat.com/show_bug.cgi?id=2005221 seems we ended up with a nasty bug in 4.4.8, We will be releasing 4.4.8.6 shortly, but it won’t fix the problem for those who already upgraded. If you have a Windows VM, can you please check "Hardware Clock Time Offset” in Edit VM/System, whther it has default GMT or a different value that you have set before - assuming that you did. For Windows people usually set it to their local time zone. For the HE problem, can you try to actually edit that VM and change something (something that’s changeable, e.g. description) and save it? Regardless if that works, can you try to restart HE (by moving to global maintenance, or if you don’t care too much, just shut it down from within that HE VM and let it be restarted automatically) If you have any additional logs/observation please add that to the bug Thanks, michal
On 17. 9. 2021, at 15:33, Andrea Chierici <andrea.chierici@cnaf.infn.it> wrote:
Really no suggestions at all?
Andrea
On 15/09/2021 12:33, Andrea Chierici wrote:
Dear all, I have just updated my ovirt installation, with self hosted engine, from 4.4.5 to 4.4.8.5-1. Everything went smoothly and in a few minutes the system was back up and running. A little issue is still puzzling me. I am asked to update from 4.5 to 4.6 the cluster and data center compatibility level. When I try to issue the command from the cluster config I get this error:
Error while executing action: Cannot update cluster because the update triggered update of the VMs/Templates and it failed for the following: HostedEngine. To fix the issue, please go to each of them, edit, change the Custom Compatibility Version (or other fields changed previously in the cluster dialog) and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change (or other changes). If the problem still persists, you may refer to the engine.log file for further details.
It's very strange because the config of the hostedengine is "plain" and there are no constrains on compatibility version, as you can see in this picture:
<hdledldbfdpnejpk.png>
In any case, if I try to force compatibility with 4.6 I get this error:
Error while executing action:
HostedEngine:
There was an attempt to change Hosted Engine VM values that are locked.
So I am stuck. Not a big deal at the moment, but sooner or later I will have to do this upgrade and I don't know where I am wrong.
Can anybody give a clue? Thanks in advance,
Andrea
-- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz --
_______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/BQMHMKNLPANYOI... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/BQMHMKNLPANYOIWDSLSPBB3UUY4FXRNR/>
-- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz -- _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/2WDJEQYIDZNNIK...
Hosted Engine properties cannot be edited since the upgrade. I also restarted the HE and it made no difference. Even just opening the HE properties and clicking OKAY without changing anything yields the following error: There was an attempt to change Hosted Engine VM values that are locked. Will the forthcoming 4.4.8.6 HE update (mentioned in a separate thread) fix the cluster compatibility upgrade problem?
I just upgraded the HE to 4.4.8.6 and rebooted it. I still cannot upgrade the cluster compatibility level. Cannot edit properties of the HE either. Error I receive when trying to update the compatibility level: Error while executing action: Cannot update cluster because the update triggered update of the VMs/Templates and it failed for the following: HostedEngine. To fix the issue, please go to each of them, edit, change the Custom Compatibility Version (or other fields changed previously in the cluster dialog) and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change (or other changes). If the problem still persists, you may refer to the engine.log file for further details. Error I receive when trying to edit the HE properties: There was an attempt to change Hosted Engine VM values that are locked. This is becoming very annoying. Updating is an hours-long process in my environment and has now failed twice.
On Thu, Sep 23, 2021 at 7:29 PM Diggy Mc <d03@bornfree.org> wrote:
I just upgraded the HE to 4.4.8.6 and rebooted it. I still cannot upgrade the cluster compatibility level. Cannot edit properties of the HE either.
If I understood correctly, the fix is in the sense that if not already updated to 4.4.8, the flow should be ok now. But probably to solve the problems for the guys that already updated to the "broken" 4.4.8, more work still has to be done by the developers... Gianluca
On 23. 9. 2021, at 19:35, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Thu, Sep 23, 2021 at 7:29 PM Diggy Mc <d03@bornfree.org <mailto:d03@bornfree.org>> wrote: I just upgraded the HE to 4.4.8.6 and rebooted it. I still cannot upgrade the cluster compatibility level. Cannot edit properties of the HE either.
If I understood correctly, the fix is in the sense that if not already updated to 4.4.8, the flow should be ok now.
correct
But probably to solve the problems for the guys that already updated to the "broken" 4.4.8, more work still has to be done by the developers...
yeah, it can’t be fixed that easily once it happens. Probably time for direct database update…. Assuming that you don’t have VMs with different TZs then change all Windwos VMs to your local TZ(here EST) with # /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "update vm_static SET time_zone='Eastern Standard Time' where os in ('1','3','4','10','11','12','16','17','20','21','23','25','26','27','29','31')"; And also for all non-Windows VMs to 'Etc/GMT’ with # /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "update vm_static SET time_zone='Etc/GMT' where os not in ('1','3','4','10','11','12','16','17','20','21','23','25','26','27','29','31')”; That will cover HostedEngine as well, and it should fix the CL update problem. Caveat - I havent’ tried that and it’s not tested. Doublecheck it has been set. Zones should be from https://github.com/oVirt/ovirt-engine/blob/master/packaging/conf/timezones-d... Hope it helps, michal
Gianluca _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/LBUHSVAZIFCAT3...
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.
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? 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? Thanks, Gianluca On Thu, Sep 23, 2021 at 9:45 PM Diggy Mc <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. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TNM4W25ECQKXRX...
On 24. 9. 2021, at 9:43, Gianluca Cecchi <gianluca.cecchi@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@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';
_______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TNM4W25ECQKXRX... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/TNM4W25ECQKXRXCDVMXEWAD3OA3B5IDE/> _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/72BIXUGUE44Y2X...
On Fri, Sep 24, 2021 at 11:05 AM Michal Skrivanek < michal.skrivanek@redhat.com> wrote:
On 24. 9. 2021, at 9:43, Gianluca Cecchi <gianluca.cecchi@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
Of course... I meant if I have standalone external engine that manages VM1 and VM2 and I update from 4.4.7 to 4.4.8-5, will VM1 and VM2 impacted? I presume yes from your answer
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.
So I don't understand if I need to rollback or if I can anyway update to 4.4.8-6 and eventually modify from database. By the way in my env all my VMs in 4.4.7 had timezone set to the default value "Etc/GMT". Does this imply no impact at all? Eg on another environment I see that after updating from 4.4.7 to 4.4.8-5 and then 4.4.8-6, in Web Admin GUI if I select a VM, in general subtab I have for 2 of them Hardware Clock Time Offset: Etc/GMT for all the other ones there isn't the "Hardware Clock Time Offset" item... Fot these VMs under edit virtual machine -> system -> Hardware Clock Time Offset I see they have the value default:(GMTZ) Greenwich Standard Time and from database point of view: engine=# select time_zone,count(*) from vm_static group by time_zone; time_zone | count -----------+------- | 18 Etc/GMT | 2 (2 rows) engine=# engine=# select vm_name from vm_static where time_zone='Etc/GMT'; vm_name ----------- testcl1 c76client (2 rows) engine=# So I should use the db statement too, correct? Any need to restart engine service after or before that? Thanks Gianluca
On 24. 9. 2021, at 11:28, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Fri, Sep 24, 2021 at 11:05 AM Michal Skrivanek <michal.skrivanek@redhat.com <mailto:michal.skrivanek@redhat.com>> wrote:
On 24. 9. 2021, at 9:43, Gianluca Cecchi <gianluca.cecchi@gmail.com <mailto:gianluca.cecchi@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
Of course... I meant if I have standalone external engine that manages VM1 and VM2 and I update from 4.4.7 to 4.4.8-5, will VM1 and VM2 impacted? I presume yes from your answer
yes
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.
So I don't understand if I need to rollback or if I can anyway update to 4.4.8-6 and eventually modify from database. By the way in my env all my VMs in 4.4.7 had timezone set to the default value "Etc/GMT". Does this imply no impact at all?
you should set it to something. It sets it to default on its own whenever that VMs get "touched" in some way, and since Etc/GMT is the default you won't really notice much, but there might be places where it may cause issues (dunno, OVF export maybe)
Eg on another environment I see that after updating from 4.4.7 to 4.4.8-5 and then 4.4.8-6, in Web Admin GUI if I select a VM, in general subtab I have for 2 of them
Hardware Clock Time Offset: Etc/GMT
for all the other ones there isn't the "Hardware Clock Time Offset" item... Fot these VMs under edit virtual machine -> system -> Hardware Clock Time Offset I see they have the value default:(GMTZ) Greenwich Standard Time
and from database point of view:
engine=# select time_zone,count(*) from vm_static group by time_zone; time_zone | count -----------+------- | 18 Etc/GMT | 2 (2 rows)
engine=#
engine=# select vm_name from vm_static where time_zone='Etc/GMT'; vm_name ----------- testcl1 c76client (2 rows)
yeah, so those are vms which you have probably edited and saved in the meantime.
engine=#
So I should use the db statement too, correct?
Hard to say, to minimize changes HE might be enough as long as you do not see any other issues anywhere else and you would use the default anyway.
Any need to restart engine service after or before that?
Not really needed. Thanks, michal
Thanks Gianluca
I too am having the exact same problem. The HE and all hosts are now at 4.4.8 and seem to be running fine. Cannot upgrade cluster compatibility level though because of something to do with the HE. Kind of annoying since it is the last thing to do to complete the upgrade. Hmph...
Thanks everyone for all the support. After fixing the TZ for the HE, I was able to upgrade cluster compatibility. Having said that, I still had to go through the properties of over 100 VMs to verify/correct the TZ because of that nasty bug. And of course I had to deal with the VirtIO re-enumeration problem affecting all my Windows VMs because of the compatibility level upgrade. Fortunately there are very few Windows VMs. Mostly a Linux shop here. :) Thanks again. Have a great weekend.
participants (5)
-
Andrea Chierici -
Diggy Mc -
Gianluca Cecchi -
Michal Skrivanek -
Strahil Nikolov