upgrade from 4.38 to 4.39
I read documentation on upgrade procedures for minor upgrades. Before I begin, I wanted to know of any issues or special procedures I need to follow. Please advise. I appreciate any advice or guidance. Thank you. Eric
On March 7, 2020 6:07:51 PM GMT+02:00, eevans@digitaldatatechs.com wrote:
I read documentation on upgrade procedures for minor upgrades. Before I begin, I wanted to know of any issues or special procedures I need to follow. Please advise. I appreciate any advice or guidance. Thank you. Eric _______________________________________________ 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/B2VX4OMNQCJV6H...
Hi Eric, If you use gluster for your HostedEngine's storage domain (and you didn't add any VMs there) - shutdown the VM and make a snapshot before the patch ... Just in case. Patch the engine , then the hosts. If you have intel-based cpu hosts, you might hit some spectre fixes. Once a node is patched do basic test (at least) - stop a VM, start a VM, make a snapshot, delete the snapshot, live migration... Something like that. If it's OK, you can procceed with the next node and repeat. Best Regards, Strahil Nikolov
The upgrade went successfully, however I have lost the ability to migrate vm's manually. The engine log: 2020-03-07 15:05:32,826-05 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] (EE-ManagedThreadFactory-engineScheduled-Thread-58) [] Fetched 0 VMs from VDS '3e4e1779-045d-4cee-be45-99a80471a1e4' 2020-03-07 15:05:59,675-05 WARN [org.ovirt.engine.core.bll.SearchQuery] (default task-5) [f2f9faa4-41ac-475b-ad57-cb17792d4c77] ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : id='' 2020-03-07 15:07:31,640-05 WARN [org.ovirt.engine.core.bll.SearchQuery] (default task-5) [edce2f10-d670-4e7e-a69a-937d91882146] ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : id='' If I put a host into maintenance the vm's migrate automatically.But manual migration is broken for some reason. Any ideas?
On March 7, 2020 10:11:13 PM GMT+02:00, eevans@digitaldatatechs.com wrote:
The upgrade went successfully, however I have lost the ability to migrate vm's manually. The engine log: 2020-03-07 15:05:32,826-05 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] (EE-ManagedThreadFactory-engineScheduled-Thread-58) [] Fetched 0 VMs from VDS '3e4e1779-045d-4cee-be45-99a80471a1e4' 2020-03-07 15:05:59,675-05 WARN [org.ovirt.engine.core.bll.SearchQuery] (default task-5) [f2f9faa4-41ac-475b-ad57-cb17792d4c77] ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : id='' 2020-03-07 15:07:31,640-05 WARN [org.ovirt.engine.core.bll.SearchQuery] (default task-5) [edce2f10-d670-4e7e-a69a-937d91882146] ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : id='' If I put a host into maintenance the vm's migrate automatically.But manual migration is broken for some reason. Any ideas? _______________________________________________ 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/KKWY5FAL2FZRU2...
Check the libvirt log. Sometimes it gives more clues: /var/log/libvirt/qemu/<VMname>.log Also, check if it can be done via the API. If API works, core functionality is OK and only UI is affected. Best Regards, Strahil Nikolov
On Sat, Mar 7, 2020 at 11:19 PM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
On March 7, 2020 10:11:13 PM GMT+02:00, eevans@digitaldatatechs.com wrote:
The upgrade went successfully, however I have lost the ability to migrate vm's manually. The engine log: 2020-03-07 15:05:32,826-05 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] (EE-ManagedThreadFactory-engineScheduled-Thread-58) [] Fetched 0 VMs from VDS '3e4e1779-045d-4cee-be45-99a80471a1e4' 2020-03-07 15:05:59,675-05 WARN [org.ovirt.engine.core.bll.SearchQuery] (default task-5) [f2f9faa4-41ac-475b-ad57-cb17792d4c77] ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : id='' 2020-03-07 15:07:31,640-05 WARN [org.ovirt.engine.core.bll.SearchQuery] (default task-5) [edce2f10-d670-4e7e-a69a-937d91882146] ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : id='' If I put a host into maintenance the vm's migrate automatically.But manual migration is broken for some reason. Any ideas?
Are you sure that above is all you get in engine.log when trying to migrate? Please try again and check/share engine.log over all the relevant time interval.
_______________________________________________ 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/KKWY5FAL2FZRU2...
Check the libvirt log. Sometimes it gives more clues:
/var/log/libvirt/qemu/<VMname>.log
Also, check if it can be done via the API. If API works, core functionality is OK and only UI is affected.
Best Regards, Strahil Nikolov _______________________________________________ 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/SW6X2EBB5RLCRL...
-- Didi
participants (3)
-
eevans＠digitaldatatechs.com -
Strahil Nikolov -
Yedidyah Bar David