On Tue, Sep 8, 2020 at 4:33 AM ddqlo <[email protected]> wrote: > my hosts cpu:Intel Haswell-noTSX Family > > cluster cpu:Intel Haswell-noTSX Family > HostedEngine vm cpu:Intel Haswell-noTSX Family > > When I tried to put the host in maintenance in web UI, I got an error: > > Adding Arik. Arik - any idea what else to test?
> > When I typed the command, I got this: > > [root@node22 ~]# hosted-engine --set-maintenance --mode=local > > Unable to enter local maintenance mode: the engine VM is running on the > current host, please migrate it before entering local maintenance mode. > Sorry, I wasn't aware that this was disabled since 4.3.5, about a year ago: https://gerrit.ovirt.org/#/q/Ia06b9bc6e65a7937e6d6462c001b59572369fe66,n,z So you'll have to first fix migration on engine level. Best regards, > > > > At 2020-09-07 12:52:01, "Yedidyah Bar David" <[email protected]> wrote: > >On Mon, Sep 7, 2020 at 4:13 AM ddqlo <[email protected]> wrote: > >> > >> I have found some engine logs: > >> > >> 2020-09-07 09:00:45,428+08 INFO > >> [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-6) > >> [29259482-1515-4c10-8458-59354a0953ac] Candidate host 'node22' > >> ('585b374b-4c82-4f5c-aad7-196d9f5d5625') was filtered out by > >> 'VAR__FILTERTYPE__INTERNAL' filter 'CPU' (correlation id: null) > >> > >> 2020-09-07 09:00:45,428+08 INFO > >> [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-6) > >> [29259482-1515-4c10-8458-59354a0953ac] Candidate host 'node28' > >> ('a678a15d-19e6-46f2-80bf-c3181197a0a6') was filtered out by > >> 'VAR__FILTERTYPE__INTERNAL' filter 'CPU' (correlation id: null) > >> > >> > >> It seems that both of the two hosts were filtered out. > > > >So please check cpu conf of the hosts, cluster, VM, etc. > > > >One more thing you can try is to force putting the host in maintenance > >- this will require migrating the engine VM. > > > >If the engine refuses to do that, because it can't migrate the VM due > >to above issue, you can try instead: > > > >hosted-engine --set-maintenance --mode=local > > > >I think this overrides the engine and will force a migration. Didn't > >try recently. > > > >Best regards, > > > >> > >> > >> > >> > >> 在 2020-09-07 07:50:55，"ddqlo" <[email protected]> 写道： > >> > >> I could not find any logs because the migration button is disabled in the > >> web UI. It seems that the engine migration operation is prevented at > >> first. Any other ideas? Thanks! > >> > >> > >> > >> > >> > >> > >> > >> 在 2020-09-01 00:06:19，"Strahil Nikolov" <[email protected]> 写道： > >> >I'm running oVirt 4.3.10 and I can migrate my Engine from node to node. > >> >I had one similar issue , but powering off and on the HE has fixed it. > >> > > >> >You have to check the vdsm log on the source and on destination in order > >> >to figure out what is going on. > >> >Also you might consider checking the libvirt logs on the destination. > >> > > >> >Best Regards, > >> >Strahil Nikolov > >> > > >> > > >> > > >> > > >> > > >> > > >> >В понеделник, 31 август 2020 г., 10:47:22 Гринуич+3, ddqlo > >> ><[email protected]> написа: > >> > > >> > > >> > > >> > > >> > > >> >Thanks! The scores of all nodes are not '0'. I find that someone has > >> >already asked a question like this. It seems that this feature has been > >> >disabled in 4.3. I am not sure if it is enabled in 4.4. > >> > > >> > > >> >在 2020-08-29 02:27:03，"Strahil Nikolov" <[email protected]> ： > >> >>Have you checked under a shell the output of 'hosted-engine --vm-status' > >> >>. Check the Score of the hosts. Maybe there is a node with score of '0' ? > >> >> > >> >>Best Regards, > >> >>Strahil Nikolov > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >>В вторник, 25 август 2020 г., 13:46:18 Гринуич+3, 董青龙 <[email protected]> > >> >>написа: > >> >> > >> >> > >> >> > >> >> > >> >> > >> >>Hi all, > >> >> I have an ovirt4.3.10.4 environment of 2 hosts. Normal vms in > >> >> this environment could be migrated, but the hosted engine vm could not > >> >> be migrated. Anyone can help? Thanks a lot! > >> >> > >> >>hosts status: > >> >> > >> >>normal vm migration: > >> >> > >> >>hosted engine vm migration: > >> >> > >> >> > >> >> > >> >> > >> >>_______________________________________________ > >> >>Users mailing list -- [email protected] > >> >>To unsubscribe send an email to [email protected] > >> >>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/[email protected]/message/ZXHE2AJX42HNHOMYHTDCUUIU3VQTQTLF/ > >> > > >> > > >> > > >> > > >> > > >> >_______________________________________________ > >> >Users mailing list -- [email protected] > >> >To unsubscribe send an email to [email protected] > >> >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/[email protected]/message/IAYLFLC6K42OUPZSZU3P3ZYAU66LGSCD/ > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> _______________________________________________ > >> Users mailing list -- [email protected] > >> To unsubscribe send an email to [email protected] > >> 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/[email protected]/message/HRCQR7Y6AMUW6HAVINQVSIRB6B6WGXMN/ > > > > > > > >-- > >Didi > > > > > -- Didi
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/DPNXPLOQXCP6WJT5HUFUANZAABJFGATZ/
