Need some magic here ...
- 2 hosts CentOS 7.5.1804 with all the patch available, in the cluster
- hosted engine from rpm ovirt-engine-appliance-4.2-20181113.1.el7.noarch with all the
patch as well (manager Version 18.104.22.168-1.el7)
1) I re-install the hosts and the hosted engine from scratch
2) I imported the ISO, export and DATA domain from the SAN
3) I went to the DATA domain in the VM Import tab where I saw all the VMs
4) I imported the VM one after one BUT ....
One of the VM (Windows 10 x64) can't be import because of the error in the subject of
this thread. In the engine.log file I get
2018-12-01 19:17:50,387-05 WARN
[org.ovirt.engine.core.bll.exportimport.ImportVmFromConfigurationCommand] (default task-4)
[92c96b3c-38c5-42ab-b81c-11413ea32ccd] Validation of action
'ImportVmFromConfiguration' failed for user admin@internal-authz. Reasons:
So it seem that the timezone of the VM is not a valid timezone so I used engine-config
engine-config -s DefaultWindowsTimeZone="Eastern Standard Time"
and restart the engine service and try again to import without success
engine-config -s DefaultWindowsTimeZone="GMT Standard Time"
and restart again and import again no success
I tried all the timezone available for Windows and always the same result. I also tried
to put the DefaultWindowsTimeZone empty but engine-config doesn't allow that neither
if I put a *
The VM is on iscsi device so can't go see the vm files to fix it directly on the fs
10 hours since I start to fix this import thing ;-(
If someone has some magic for me, I will be a nice gift before christmas
Show replies by date
I restore the engine DB on another server to look at the time_zone for the faulty server
and here what I have
America/New_York but it's not valid for a Windows VM. Windows VM get time_zone like
"GMT Standard Time", "Eastern Standard Time", etc but no time_zone
with a / in the name like Linux time_zone.
Now, how can I get to the ISCSI drive to change this time_zone and be able to import the
VM after ?