- Users - oVirt List Archives

TR: HA/Live Migration problems
by CABRIMOL Steven 13 Jun '17

13 Jun '17

This is a multi-part message in MIME format. ------=_NextPart_000_003D_01D2E468.6B6F3E70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 =20 _____ =20 De : CABRIMOL Steven [mailto:steven.cabrimol@c-s.fr]=20 Envoy=E9 : mardi 13 juin 2017 17:06 =C0 : 'users(a)ovirt.org' Objet : HA/Live Migration problems =20 Hi guys, =20 I do not know if it=92s the right place to ask, but it seems you don=92t = have any user forum, so : I just install O=92virt and all the basics functions seems to be ok BUT = I can=92t do Live migration, and HA is just reboot my host but not the = VM=92s.=20 =20 Features Working : =20 2x Hypervisors : power management is ok 2x DATA STORAGE : VM storage and Hosted-engine storage 1x Cluster 2x Centos7 VM : guest-agent install =20 * I can do cold migration on both hypervisor. * The two hypervisor see the storage =20 =20 =20 I maybe/surely miss something=85. ( I don=92t found any real how-to for = my type of infra)=20 =20 =20 PS : Just now it work on one side FIFI to RIRI, but not on the other = one=85 =20 =20 Hope you can help me, enjoy your day. =20 Bye =20 Log : ( engine.log) =20 2017-06-13 15:04:08,501+02 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-8) [37ac066c-6732-4817-99cc-87f954ad09d9] Lock Acquired to object 'EngineLock:{exclusiveLocks=3D'[a5cf6fc3-17dc-45f2-b81f-cb9179df132b=3D<V= M, ACTION_TYPE_FAILED_VM_IS_BEING_MIGRATED$VmName HostedEngine>]', sharedLocks=3D'null'}' 2017-06-13 15:04:08,861+02 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (org.ovirt.thread.pool-6-thread-22) = [37ac066c-6732-4817-99cc-87f954ad09d9] Running command: MigrateVmToServerCommand internal: false. Entities = affected : ID: a5cf6fc3-17dc-45f2-b81f-cb9179df132b Type: VMAction group = MIGRATE_VM with role type USER 2017-06-13 15:04:09,234+02 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (org.ovirt.thread.pool-6-thread-22) = [37ac066c-6732-4817-99cc-87f954ad09d9] START, MigrateVDSCommand( = MigrateVDSCommandParameters:{runAsync=3D'true', hostId=3D'f5523fc0-be7b-4097-a987-bc1902acab84', vmId=3D'a5cf6fc3-17dc-45f2-b81f-cb9179df132b', srcHost=3D'fifi', dstVdsId=3D'87e118d8-5331-4b5e-8fd1-c5e7ef91e687', dstHost=3D'172.17.74.216:54321', migrationMethod=3D'ONLINE', tunnelMigration=3D'false', migrationDowntime=3D'0', = autoConverge=3D'false', migrateCompressed=3D'false', consoleAddress=3D'null', = maxBandwidth=3D'50', enableGuestEvents=3D'false', maxIncomingMigrations=3D'2', maxOutgoingMigrations=3D'2', convergenceSchedule=3D'null'}), log id: = 1abe8132 2017-06-13 15:04:09,234+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (org.ovirt.thread.pool-6-thread-22) = [37ac066c-6732-4817-99cc-87f954ad09d9] START, MigrateBrokerVDSCommand(HostName =3D fifi, MigrateVDSCommandParameters:{runAsync=3D'true', hostId=3D'f5523fc0-be7b-4097-a987-bc1902acab84', vmId=3D'a5cf6fc3-17dc-45f2-b81f-cb9179df132b', srcHost=3D'fifi', dstVdsId=3D'87e118d8-5331-4b5e-8fd1-c5e7ef91e687', dstHost=3D'172.17.74.216:54321', migrationMethod=3D'ONLINE', tunnelMigration=3D'false', migrationDowntime=3D'0', = autoConverge=3D'false', migrateCompressed=3D'false', consoleAddress=3D'null', = maxBandwidth=3D'50', enableGuestEvents=3D'false', maxIncomingMigrations=3D'2', maxOutgoingMigrations=3D'2', convergenceSchedule=3D'null'}), log id: = 1a2a6cdc 2017-06-13 15:04:10,068+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (org.ovirt.thread.pool-6-thread-22) = [37ac066c-6732-4817-99cc-87f954ad09d9] FINISH, MigrateBrokerVDSCommand, log id: 1a2a6cdc 2017-06-13 15:04:10,084+02 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (org.ovirt.thread.pool-6-thread-22) = [37ac066c-6732-4817-99cc-87f954ad09d9] FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 1abe8132 2017-06-13 15:04:10,127+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-22) = [37ac066c-6732-4817-99cc-87f954ad09d9] EVENT_ID: VM_MIGRATION_START(62), Correlation ID: 37ac066c-6732-4817-99cc-87f954ad09d9, Job ID: d625be6c-f91f-4200-accc-3cf4a0e5aa77, Call Stack: null, Custom Event ID: = -1, Message: Migration started (VM: HostedEngine, Source: fifi, Destination: RIRI, User: admin(a)internal-authz).=20 2017-06-13 15:04:15,219+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] (DefaultQuartzScheduler1) [] Fetched 2 VMs from VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687' 2017-06-13 15:04:15,223+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:04:15,223+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:04:30,525+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:04:30,525+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:04:46,070+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:04:46,070+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:05:02,321+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:05:02,321+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:05:17,377+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:05:17,377+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:05:32,417+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:05:32,417+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:05:47,706+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:05:47,707+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:06:04,346+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:06:04,346+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:06:19,940+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler6) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:06:19,941+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler6) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:06:35,350+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler2) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:06:35,350+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler2) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:06:50,395+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler2) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:06:50,395+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler2) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:07:05,444+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler2) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:07:05,444+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler2) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:07:21,697+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:07:21,697+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:07:39,187+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:07:39,188+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:07:54,324+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:07:54,324+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:08:09,435+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:08:09,435+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:08:25,903+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:08:25,903+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 15:08:31,980+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = was reported as Down on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) 2017-06-13 15:08:31,982+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-7) [] START, DestroyVDSCommand(HostName =3D RIRI, DestroyVmVDSCommandParameters:{runAsync=3D'true', hostId=3D'87e118d8-5331-4b5e-8fd1-c5e7ef91e687', vmId=3D'a5cf6fc3-17dc-45f2-b81f-cb9179df132b', force=3D'false', secondsToWait=3D'0', gracefully=3D'false', reason=3D'', = ignoreNoVm=3D'true'}), log id: 12dc06bb 2017-06-13 15:08:33,355+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-7) [] Failed to destroy VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' because VM does not exist, = ignoring 2017-06-13 15:08:33,355+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-7) [] FINISH, DestroyVDSCommand, log id: 12dc06bb 2017-06-13 15:08:33,356+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'Down' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 15:08:35,626+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) moved from 'MigratingFrom' --> 'Up' 2017-06-13 15:08:35,626+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler7) [] Adding VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) to re-run list 2017-06-13 15:08:35,897+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (DefaultQuartzScheduler7) [] Rerun VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'. Called from VDS 'fifi' 2017-06-13 15:08:36,007+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (org.ovirt.thread.pool-6-thread-40) [] START, MigrateStatusVDSCommand(HostName =3D fifi, MigrateStatusVDSCommandParameters:{runAsync=3D'true', hostId=3D'f5523fc0-be7b-4097-a987-bc1902acab84', vmId=3D'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'}), log id: e3a2d40 2017-06-13 15:08:37,017+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (org.ovirt.thread.pool-6-thread-40) [] FINISH, MigrateStatusVDSCommand, = log id: e3a2d40 2017-06-13 15:08:37,065+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-40) [] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Correlation ID: 37ac066c-6732-4817-99cc-87f954ad09d9, Job ID: d625be6c-f91f-4200-accc-3cf4a0e5aa77, Call Stack: null, Custom Event ID: = -1, Message: Migration failed (VM: HostedEngine, Source: fifi, Destination: RIRI). 2017-06-13 15:08:37,086+02 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (org.ovirt.thread.pool-6-thread-40) [] Lock freed to object 'EngineLock:{exclusiveLocks=3D'[a5cf6fc3-17dc-45f2-b81f-cb9179df132b=3D<V= M, ACTION_TYPE_FAILED_VM_IS_BEING_MIGRATED$VmName HostedEngine>]', sharedLocks=3D'null'}' 2017-06-13 15:08:40,955+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] (DefaultQuartzScheduler10) [] Fetched 1 VMs from VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687' 2017-06-13 15:10:07,333+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = was reported as Down on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) 2017-06-13 15:10:07,334+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-9) [] START, DestroyVDSCommand(HostName =3D RIRI, DestroyVmVDSCommandParameters:{runAsync=3D'true', hostId=3D'87e118d8-5331-4b5e-8fd1-c5e7ef91e687', vmId=3D'a5cf6fc3-17dc-45f2-b81f-cb9179df132b', force=3D'false', secondsToWait=3D'0', gracefully=3D'false', reason=3D'', = ignoreNoVm=3D'true'}), log id: b2388b7 2017-06-13 15:10:08,482+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-9) [] FINISH, DestroyVDSCommand, log id: b2388b7 2017-06-13 15:10:08,482+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'Down' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') =20 =20 =20 LOG migration ok FIFI to RIRI =20 =20 2017-06-13 16:45:40,555+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b'(VM-RIRI) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 16:45:40,556+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 16:45:56,565+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b'(VM-RIRI) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 16:45:56,565+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 16:46:12,037+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler3) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b'(VM-RIRI) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 16:46:12,038+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler3) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done 2017-06-13 16:46:22,993+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-13) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b'(VM-RIRI) was unexpectedly = detected as 'Up' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84') 2017-06-13 16:46:23,101+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-13) [] EVENT_ID: VM_MIGRATION_DONE(63), = Correlation ID: 3ca17cc1-fed4-48a7-a23e-fc3ac8494041, Job ID: 9f6863d5-08c0-4e4d-a809-4a2d2282ddbc, Call Stack: null, Custom Event ID: = -1, Message: Migration completed (VM: VM-RIRI, Source: fifi, Destination: = RIRI, Duration: 1 minute 32 seconds, Total: 1 minute 32 seconds, Actual = downtime: 169ms) 2017-06-13 16:46:23,119+02 INFO [org.ovirt.engine.core.bll.MigrateVmCommand] (ForkJoinPool-1-worker-13) = [] Lock freed to object 'EngineLock:{exclusiveLocks=3D'[c6c3f049-ae61-4227-839e-9f70d29e910b=3D<V= M, ACTION_TYPE_FAILED_VM_IS_BEING_MIGRATED$VmName VM-RIRI>]', sharedLocks=3D'null'}' 2017-06-13 16:46:23,120+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand] (ForkJoinPool-1-worker-13) [] START, FullListVDSCommand(HostName =3D = RIRI, FullListVDSCommandParameters:{runAsync=3D'true', hostId=3D'87e118d8-5331-4b5e-8fd1-c5e7ef91e687', vmIds=3D'[c6c3f049-ae61-4227-839e-9f70d29e910b]'}), log id: 7d4624e8 2017-06-13 16:46:23,138+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand] (ForkJoinPool-1-worker-13) [] FINISH, FullListVDSCommand, return: [{acpiEnable=3Dtrue, emulatedMachine=3Dpc-i440fx-rhel7.3.0, afterMigrationStatus=3D, pid=3D7672, memGuaranteedSize=3D2048, transparentHugePages=3Dtrue, timeOffset=3D0, cpuType=3DSandyBridge, = smp=3D1, guestNumaNodes=3D[Ljava.lang.Object;@260ce3e2, smartcardEnable=3Dfalse, custom=3D{device_bbf0e81a-d9a5-40a4-a938-7f19c2b172f3=3DVmDevice:{id=3D'V= mDeviceId :{deviceId=3D'bbf0e81a-d9a5-40a4-a938-7f19c2b172f3', vmId=3D'c6c3f049-ae61-4227-839e-9f70d29e910b'}', device=3D'ide', type=3D'CONTROLLER', bootOrder=3D'0', specParams=3D'[]', = address=3D'{slot=3D0x01, bus=3D0x00, domain=3D0x0000, type=3Dpci, function=3D0x1}', = managed=3D'false', plugged=3D'true', readOnly=3D'false', deviceAlias=3D'ide', = customProperties=3D'[]', snapshotId=3D'null', logicalName=3D'null', hostDevice=3D'null'}, device_bbf0e81a-d9a5-40a4-a938-7f19c2b172f3device_08c7d5ca-049b-456e-8fdd= -8b 3bb6718d2adevice_9864e069-930b-49c3-aef2-6f297f6f67ce=3DVmDevice:{id=3D'V= mDevice Id:{deviceId=3D'9864e069-930b-49c3-aef2-6f297f6f67ce', vmId=3D'c6c3f049-ae61-4227-839e-9f70d29e910b'}', device=3D'unix', type=3D'CHANNEL', bootOrder=3D'0', specParams=3D'[]', = address=3D'{bus=3D0, controller=3D0, type=3Dvirtio-serial, port=3D2}', managed=3D'false', = plugged=3D'true', readOnly=3D'false', deviceAlias=3D'channel1', customProperties=3D'[]', snapshotId=3D'null', logicalName=3D'null', hostDevice=3D'null'}, device_bbf0e81a-d9a5-40a4-a938-7f19c2b172f3device_08c7d5ca-049b-456e-8fdd= -8b 3bb6718d2adevice_9864e069-930b-49c3-aef2-6f297f6f67cedevice_28ac518a-f30a= -4c 77-9033-dbf664d8b294=3DVmDevice:{id=3D'VmDeviceId:{deviceId=3D'28ac518a-f= 30a-4c77- 9033-dbf664d8b294', vmId=3D'c6c3f049-ae61-4227-839e-9f70d29e910b'}', device=3D'spicevmc', type=3D'CHANNEL', bootOrder=3D'0', = specParams=3D'[]', address=3D'{bus=3D0, controller=3D0, type=3Dvirtio-serial, port=3D3}', managed=3D'false', plugged=3D'true', readOnly=3D'false', = deviceAlias=3D'channel2', customProperties=3D'[]', snapshotId=3D'null', logicalName=3D'null', hostDevice=3D'null'}, device_bbf0e81a-d9a5-40a4-a938-7f19c2b172f3device_08c7d5ca-049b-456e-8fdd= -8b 3bb6718d2a=3DVmDevice:{id=3D'VmDeviceId:{deviceId=3D'08c7d5ca-049b-456e-8= fdd-8b3bb 6718d2a', vmId=3D'c6c3f049-ae61-4227-839e-9f70d29e910b'}', = device=3D'unix', type=3D'CHANNEL', bootOrder=3D'0', specParams=3D'[]', = address=3D'{bus=3D0, controller=3D0, type=3Dvirtio-serial, port=3D1}', managed=3D'false', = plugged=3D'true', readOnly=3D'false', deviceAlias=3D'channel0', customProperties=3D'[]', snapshotId=3D'null', logicalName=3D'null', hostDevice=3D'null'}}, = vmType=3Dkvm, memSize=3D2048, smpCoresPerSocket=3D1, vmName=3DVM-RIRI, nice=3D0, = status=3DUp, maxMemSize=3D8192, bootMenuEnable=3Dtrue, vmId=3Dc6c3f049-ae61-4227-839e-9f70d29e910b, smpThreadsPerCore=3D1, guestDiskMapping=3D{}, maxMemSlots=3D16, kvmEnable=3Dtrue, displayNetwork=3Dovirtmgmt, devices=3D[Ljava.lang.Object;@2e2fc0fa, = maxVCpus=3D16, clientIp=3D, statusTime=3D4372160030, display=3Dqxl}], log id: 7d4624e8 2017-06-13 16:46:23,146+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmDevicesMonitoring] (ForkJoinPool-1-worker-13) [] Received a spice Device without an address when processing VM c6c3f049-ae61-4227-839e-9f70d29e910b devices, = skipping device: {device=3Dspice, specParams=3D{fileTransferEnable=3Dtrue, displayNetwork=3Dovirtmgmt, spiceSecureChannels=3Dsmain,sinputs,scursor,splayback,srecord,sdisplay,ss= martc ard,susbredir, displayIp=3D172.17.74.216, copyPasteEnable=3Dtrue}, type=3Dgraphics, deviceId=3D84364ae9-1984-4d24-bc5b-aa3969502205, = tlsPort=3D5900} 2017-06-13 16:46:23,244+02 INFO [org.ovirt.engine.core.bll.VmSlaPolicyCommand] (org.ovirt.thread.pool-6-thread-38) [6ab21bc6] Running command: VmSlaPolicyCommand internal: true. Entities affected : ID: c6c3f049-ae61-4227-839e-9f70d29e910b Type: VMAction group = EDIT_VM_PROPERTIES with role type USER 2017-06-13 16:46:23,245+02 INFO [org.ovirt.engine.core.vdsbroker.UpdateVmPolicyVDSCommand] (org.ovirt.thread.pool-6-thread-38) [6ab21bc6] START, UpdateVmPolicyVDSCommand(HostName =3D RIRI, UpdateVmPolicyVDSParams:{runAsync=3D'true', hostId=3D'87e118d8-5331-4b5e-8fd1-c5e7ef91e687', vmId=3D'c6c3f049-ae61-4227-839e-9f70d29e910b'}), log id: 12ae92d2 2017-06-13 16:46:24,250+02 INFO [org.ovirt.engine.core.vdsbroker.UpdateVmPolicyVDSCommand] (org.ovirt.thread.pool-6-thread-38) [6ab21bc6] FINISH, UpdateVmPolicyVDSCommand, log id: 12ae92d2 2017-06-13 16:46:24,326+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-38) [6ab21bc6] EVENT_ID: VM_SLA_POLICY_CPU(10,550), Correlation ID: 6ab21bc6, Call Stack: null, Custom Event ID: -1, Message: VM VM-RIRI SLA Policy was set. CPU limit = is set to 10 2017-06-13 16:46:29,942+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler4) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b' = was reported as Down on VDS 'f5523fc0-be7b-4097-a987-bc1902acab84'(fifi) 2017-06-13 16:46:29,943+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (DefaultQuartzScheduler4) [] START, DestroyVDSCommand(HostName =3D fifi, DestroyVmVDSCommandParameters:{runAsync=3D'true', hostId=3D'f5523fc0-be7b-4097-a987-bc1902acab84', vmId=3D'c6c3f049-ae61-4227-839e-9f70d29e910b', force=3D'false', secondsToWait=3D'0', gracefully=3D'false', reason=3D'', = ignoreNoVm=3D'true'}), log id: 4666101e 2017-06-13 16:46:31,175+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (DefaultQuartzScheduler4) [] FINISH, DestroyVDSCommand, log id: 4666101e 2017-06-13 16:46:31,175+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler4) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b'(VM-RIRI) was unexpectedly = detected as 'Down' on VDS 'f5523fc0-be7b-4097-a987-bc1902acab84'(fifi) (expected on '87e118d8-5331-4b5e-8fd1-c5e7ef91e687') 2017-06-13 16:46:48,001+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] (DefaultQuartzScheduler2) [] Fetched 2 VMs from VDS 'f5523fc0-be7b-4097-a987-bc1902acab84' ------=_NextPart_000_003D_01D2E468.6B6F3E70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">  <style>  </style> </head> <body lang=3DFR link=3Dblue vlink=3Dpurple> <div class=3DSection1> <o:p> </o:p> <o:p> </o:p> <div> <div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'> <hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1> </div> De : = CABRIMOL Steven [mailto:steven.cabrimol@c-s.fr] Envoyé : = mardi 13 juin 2017 17:06 À : = 'users(a)ovirt.org' Objet : HA/Live = Migration problems<o:p></o:p> </div> <o:p> </o:p> Hi guys,<o:p></o:p> <o:p> </o:p> I do not know if it’s the right place to = ask, but it seems you don’t have any user forum, so = :<o:p></o:p> I just install O’virt and all the basics functions seems to be ok BUT I = can’t do Live migration, and HA is = just reboot my host but not the VM’s. = <o:p></o:p> <o:p> </o:p> Features Working = :<o:p></o:p> <o:p> </o:p> 2x Hypervisors : power management is = ok<o:p></o:p> 2x DATA STORAGE : VM storage and Hosted-engine storage<o:p></o:p> 1x Cluster<o:p></o:p> 2x Centos7 VM : guest-agent = install<o:p></o:p> <o:p> </o:p> <ul style=3D'margin-top:0cm' type=3Ddisc> <li class=3DMsoNormal style=3D'mso-list:l1 level1 lfo3'>I can do = cold migration on both hypervisor.<o:p></o:p></li> <li class=3DMsoNormal style=3D'mso-list:l1 level1 lfo3'>The two = hypervisor see the storage<o:p></o:p></li> </ul> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> I maybe/surely miss something…. ( I don’t found any real = how-to for my type of infra) <o:p></o:p> <o:p> </o:p> <o:p> </o:p> PS : Just = now it work on one side FIFI to RIRI, but not on the other = one…<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Hope you can help me, enjoy your = day.<o:p></o:p> <o:p> </o:p> Bye<o:p></o:p> <o:p> </o:p></fo= nt> Log :  ( = engine.log)<o:p></o:p> <o:p> </o:p> 2017-06-13 15:04:08,501+02 INFO  [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-8) [37ac066c-6732-4817-99cc-87f954ad09d9] Lock Acquired to object 'EngineLock:{exclusiveLocks=3D'[a5cf6fc3-17dc-45f2-b81f-cb9179df132b=3D&l= t;VM, ACTION_TYPE_FAILED_VM_IS_BEING_MIGRATED$VmName HostedEngine>]', sharedLocks=3D'null'}'<o:p></o:p> 2017-06-13 15:04:08,861+02 INFO  [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (org.ovirt.thread.pool-6-thread-22) = [37ac066c-6732-4817-99cc-87f954ad09d9] Running command: MigrateVmToServerCommand internal: false. Entities = affected :  ID: a5cf6fc3-17dc-45f2-b81f-cb9179df132b Type: VMAction group MIGRATE_VM with role type USER<o:p></o:p> 2017-06-13 15:04:09,234+02 INFO  [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (org.ovirt.thread.pool-6-thread-22) = [37ac066c-6732-4817-99cc-87f954ad09d9] START, MigrateVDSCommand( = MigrateVDSCommandParameters:{runAsync=3D'true', hostId=3D'f5523fc0-be7b-4097-a987-bc1902acab84', vmId=3D'a5cf6fc3-17dc-45f2-b81f-cb9179df132b', srcHost=3D'fifi', dstVdsId=3D'87e118d8-5331-4b5e-8fd1-c5e7ef91e687', = dstHost=3D'172.17.74.216:54321', migrationMethod=3D'ONLINE', tunnelMigration=3D'false', = migrationDowntime=3D'0', autoConverge=3D'false', migrateCompressed=3D'false', = consoleAddress=3D'null', maxBandwidth=3D'50', enableGuestEvents=3D'false', = maxIncomingMigrations=3D'2', maxOutgoingMigrations=3D'2', convergenceSchedule=3D'null'}), log id: = 1abe8132<o:p></o:p> 2017-06-13 15:04:09,234+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] = (org.ovirt.thread.pool-6-thread-22) [37ac066c-6732-4817-99cc-87f954ad09d9] START, = MigrateBrokerVDSCommand(HostName =3D fifi, MigrateVDSCommandParameters:{runAsync=3D'true', hostId=3D'f5523fc0-be7b-4097-a987-bc1902acab84', vmId=3D'a5cf6fc3-17dc-45f2-b81f-cb9179df132b', srcHost=3D'fifi', dstVdsId=3D'87e118d8-5331-4b5e-8fd1-c5e7ef91e687', = dstHost=3D'172.17.74.216:54321', migrationMethod=3D'ONLINE', tunnelMigration=3D'false', = migrationDowntime=3D'0', autoConverge=3D'false', migrateCompressed=3D'false', = consoleAddress=3D'null', maxBandwidth=3D'50', enableGuestEvents=3D'false', maxIncomingMigrations=3D'2', maxOutgoingMigrations=3D'2', convergenceSchedule=3D'null'}), log id: = 1a2a6cdc<o:p></o:p> 2017-06-13 15:04:10,068+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (org.ovirt.thread.pool-6-thread-22) = [37ac066c-6732-4817-99cc-87f954ad09d9] FINISH, MigrateBrokerVDSCommand, log id: = 1a2a6cdc<o:p></o:p> 2017-06-13 15:04:10,084+02 INFO  [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (org.ovirt.thread.pool-6-thread-22) = [37ac066c-6732-4817-99cc-87f954ad09d9] FINISH, MigrateVDSCommand, return: MigratingFrom, log id: = 1abe8132<o:p></o:p> 2017-06-13 15:04:10,127+02 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-22) = [37ac066c-6732-4817-99cc-87f954ad09d9] EVENT_ID: VM_MIGRATION_START(62), Correlation ID: 37ac066c-6732-4817-99cc-87f954ad09d9, Job ID: d625be6c-f91f-4200-accc-3cf4a0e5aa77, Call Stack: null, Custom Event ID: = -1, Message: Migration started (VM: HostedEngine, Source: fifi, Destination: = RIRI, User: admin@internal-authz). <o:p></o:p> 2017-06-13 15:04:15,219+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] (DefaultQuartzScheduler1) [] Fetched 2 VMs from VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'<o:p></o:p> 2017-06-13 15:04:15,223+02 INFO  = [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:04:15,223+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:04:30,525+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:04:30,525+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:04:46,070+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM = 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:04:46,070+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:05:02,321+02 INFO  = [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:05:02,321+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:05:17,377+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:05:17,377+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:05:32,417+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:05:32,417+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:05:47,706+02 INFO  = [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:05:47,707+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:06:04,346+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:06:04,346+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:06:19,940+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler6) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:06:19,941+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler6) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:06:35,350+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler2) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:06:35,350+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler2) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:06:50,395+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler2) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:06:50,395+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler2) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:07:05,444+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler2) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:07:05,444+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler2) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:07:21,697+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:07:21,697+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:07:39,187+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:07:39,188+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] = (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring it in the refresh = until migration is done<o:p></o:p> 2017-06-13 15:07:54,324+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:07:54,324+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:08:09,435+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:08:09,435+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 15:08:25,903+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM = 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:08:25,903+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] = (DefaultQuartzScheduler1) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring it in the refresh = until migration is done<o:p></o:p> 2017-06-13 15:08:31,980+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = was reported as Down on VDS = '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI)<o:p></o:p>= 2017-06-13 15:08:31,982+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] = (ForkJoinPool-1-worker-7) [] START, DestroyVDSCommand(HostName =3D RIRI, DestroyVmVDSCommandParameters:{runAsync=3D'true', hostId=3D'87e118d8-5331-4b5e-8fd1-c5e7ef91e687', vmId=3D'a5cf6fc3-17dc-45f2-b81f-cb9179df132b', force=3D'false', = secondsToWait=3D'0', gracefully=3D'false', reason=3D'', ignoreNoVm=3D'true'}), log id: = 12dc06bb<o:p></o:p> 2017-06-13 15:08:33,355+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-7) [] Failed to destroy VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' because VM does not exist, = ignoring<o:p></o:p> 2017-06-13 15:08:33,355+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-7) [] FINISH, DestroyVDSCommand, log id: = 12dc06bb<o:p></o:p> 2017-06-13 15:08:33,356+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'Down' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected = on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 15:08:35,626+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler7) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) moved from = 'MigratingFrom' --> 'Up'<o:p></o:p> 2017-06-13 15:08:35,626+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler7) [] Adding VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) to re-run = list<o:p></o:p> 2017-06-13 15:08:35,897+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (DefaultQuartzScheduler7) [] Rerun VM = 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'. Called from VDS 'fifi'<o:p></o:p> 2017-06-13 15:08:36,007+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (org.ovirt.thread.pool-6-thread-40) [] START, = MigrateStatusVDSCommand(HostName =3D fifi, MigrateStatusVDSCommandParameters:{runAsync=3D'true', hostId=3D'f5523fc0-be7b-4097-a987-bc1902acab84', vmId=3D'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'}), log id: = e3a2d40<o:p></o:p> 2017-06-13 15:08:37,017+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (org.ovirt.thread.pool-6-thread-40) [] FINISH, MigrateStatusVDSCommand, = log id: e3a2d40<o:p></o:p> 2017-06-13 15:08:37,065+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-40) [] EVENT_ID: = VM_MIGRATION_TO_SERVER_FAILED(120), Correlation ID: 37ac066c-6732-4817-99cc-87f954ad09d9, Job ID: d625be6c-f91f-4200-accc-3cf4a0e5aa77, Call Stack: null, Custom Event ID: = -1, Message: Migration failed  (VM: HostedEngine, Source: fifi, = Destination: RIRI).<o:p></o:p> 2017-06-13 15:08:37,086+02 INFO  [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (org.ovirt.thread.pool-6-thread-40) [] Lock freed to object 'EngineLock:{exclusiveLocks=3D'[a5cf6fc3-17dc-45f2-b81f-cb9179df132b=3D&l= t;VM, ACTION_TYPE_FAILED_VM_IS_BEING_MIGRATED$VmName HostedEngine>]', sharedLocks=3D'null'}'<o:p></o:p> 2017-06-13 15:08:40,955+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] (DefaultQuartzScheduler10) [] Fetched 1 VMs from VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'<o:p></o:p> 2017-06-13 15:10:07,333+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b' = was reported as Down on VDS = '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI)<o:p></o:p>= 2017-06-13 15:10:07,334+02 INFO  = [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-9) [] START, DestroyVDSCommand(HostName =3D RIRI, DestroyVmVDSCommandParameters:{runAsync=3D'true', hostId=3D'87e118d8-5331-4b5e-8fd1-c5e7ef91e687', vmId=3D'a5cf6fc3-17dc-45f2-b81f-cb9179df132b', force=3D'false', = secondsToWait=3D'0', gracefully=3D'false', reason=3D'', ignoreNoVm=3D'true'}), log id: = b2388b7<o:p></o:p> 2017-06-13 15:10:08,482+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-9) [] FINISH, DestroyVDSCommand, log id: = b2388b7<o:p></o:p> 2017-06-13 15:10:08,482+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-9) [] VM 'a5cf6fc3-17dc-45f2-b81f-cb9179df132b'(HostedEngine) was unexpectedly = detected as 'Down' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected = on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> = </o:p>  LOG  migration ok FIFI to RIRI<o:p></o:p> <o:p> = </o:p> <o:p> = </o:p> 2017-06-13 16:45:40,555+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] = (DefaultQuartzScheduler9) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b'(VM-RIRI) was unexpectedly = detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) = (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 16:45:40,556+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 16:45:56,565+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM = 'c6c3f049-ae61-4227-839e-9f70d29e910b'(VM-RIRI) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 16:45:56,565+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler9) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 16:46:12,037+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler3) [] VM = 'c6c3f049-ae61-4227-839e-9f70d29e910b'(VM-RIRI) was unexpectedly detected as 'MigratingTo' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 16:46:12,038+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler3) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b' = is migrating to VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) ignoring = it in the refresh until migration is done<o:p></o:p> 2017-06-13 16:46:22,993+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] = (ForkJoinPool-1-worker-13) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b'(VM-RIRI) was unexpectedly = detected as 'Up' on VDS '87e118d8-5331-4b5e-8fd1-c5e7ef91e687'(RIRI) (expected on 'f5523fc0-be7b-4097-a987-bc1902acab84')<o:p></o:p> 2017-06-13 16:46:23,101+02 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-13) [] EVENT_ID: VM_MIGRATION_DONE(63), = Correlation ID: 3ca17cc1-fed4-48a7-a23e-fc3ac8494041, Job ID: 9f6863d5-08c0-4e4d-a809-4a2d2282ddbc, Call Stack: null, Custom Event ID: = -1, Message: Migration completed (VM: VM-RIRI, Source: fifi, Destination: = RIRI, Duration: 1 minute 32 seconds, Total: 1 minute 32 seconds, Actual = downtime: 169ms)<o:p></o:p> 2017-06-13 16:46:23,119+02 INFO  [org.ovirt.engine.core.bll.MigrateVmCommand] (ForkJoinPool-1-worker-13) = [] Lock freed to object 'EngineLock:{exclusiveLocks=3D'[c6c3f049-ae61-4227-839e-9f70d29e910b=3D&l= t;VM, ACTION_TYPE_FAILED_VM_IS_BEING_MIGRATED$VmName VM-RIRI>]', sharedLocks=3D'null'}'<o:p></o:p> 2017-06-13 16:46:23,120+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand] (ForkJoinPool-1-worker-13) [] START, FullListVDSCommand(HostName =3D = RIRI, FullListVDSCommandParameters:{runAsync=3D'true', hostId=3D'87e118d8-5331-4b5e-8fd1-c5e7ef91e687', vmIds=3D'[c6c3f049-ae61-4227-839e-9f70d29e910b]'}), log id: = 7d4624e8<o:p></o:p> 2017-06-13 16:46:23,138+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand] (ForkJoinPool-1-worker-13) [] FINISH, FullListVDSCommand, return: [{acpiEnable=3Dtrue, emulatedMachine=3Dpc-i440fx-rhel7.3.0, = afterMigrationStatus=3D, pid=3D7672, memGuaranteedSize=3D2048, transparentHugePages=3Dtrue, = timeOffset=3D0, cpuType=3DSandyBridge, smp=3D1, = guestNumaNodes=3D[Ljava.lang.Object;@260ce3e2, smartcardEnable=3Dfalse, custom=3D{device_bbf0e81a-d9a5-40a4-a938-7f19c2b172f3=3DVmDevice:{id=3D'V= mDeviceId:{deviceId=3D'bbf0e81a-d9a5-40a4-a938-7f19c2b172f3', vmId=3D'c6c3f049-ae61-4227-839e-9f70d29e910b'}', device=3D'ide', = type=3D'CONTROLLER', bootOrder=3D'0', specParams=3D'[]', address=3D'{slot=3D0x01, bus=3D0x00, = domain=3D0x0000, type=3Dpci, function=3D0x1}', managed=3D'false', plugged=3D'true', = readOnly=3D'false', deviceAlias=3D'ide', customProperties=3D'[]', snapshotId=3D'null', logicalName=3D'null', hostDevice=3D'null'}, device_bbf0e81a-d9a5-40a4-a938-7f19c2b172f3device_08c7d5ca-049b-456e-8fdd= -8b3bb6718d2adevice_9864e069-930b-49c3-aef2-6f297f6f67ce=3DVmDevice:{id=3D= 'VmDeviceId:{deviceId=3D'9864e069-930b-49c3-aef2-6f297f6f67ce', vmId=3D'c6c3f049-ae61-4227-839e-9f70d29e910b'}', device=3D'unix', = type=3D'CHANNEL', bootOrder=3D'0', specParams=3D'[]', address=3D'{bus=3D0, controller=3D0, type=3Dvirtio-serial, port=3D2}', managed=3D'false', plugged=3D'true', readOnly=3D'false', deviceAlias=3D'channel1', customProperties=3D'[]', snapshotId=3D'null', logicalName=3D'null', hostDevice=3D'null'}, device_bbf0e81a-d9a5-40a4-a938-7f19c2b172f3device_08c7d5ca-049b-456e-8fdd= -8b3bb6718d2adevice_9864e069-930b-49c3-aef2-6f297f6f67cedevice_28ac518a-f= 30a-4c77-9033-dbf664d8b294=3DVmDevice:{id=3D'VmDeviceId:{deviceId=3D'28ac= 518a-f30a-4c77-9033-dbf664d8b294', vmId=3D'c6c3f049-ae61-4227-839e-9f70d29e910b'}', device=3D'spicevmc', type=3D'CHANNEL', bootOrder=3D'0', specParams=3D'[]', = address=3D'{bus=3D0, controller=3D0, type=3Dvirtio-serial, port=3D3}', managed=3D'false', plugged=3D'true', readOnly=3D'false', deviceAlias=3D'channel2', customProperties=3D'[]', snapshotId=3D'null', logicalName=3D'null', hostDevice=3D'null'}, device_bbf0e81a-d9a5-40a4-a938-7f19c2b172f3device_08c7d5ca-049b-456e-8fdd= -8b3bb6718d2a=3DVmDevice:{id=3D'VmDeviceId:{deviceId=3D'08c7d5ca-049b-456= e-8fdd-8b3bb6718d2a', vmId=3D'c6c3f049-ae61-4227-839e-9f70d29e910b'}', device=3D'unix', = type=3D'CHANNEL', bootOrder=3D'0', specParams=3D'[]', address=3D'{bus=3D0, controller=3D0, = type=3Dvirtio-serial, port=3D1}', managed=3D'false', plugged=3D'true', readOnly=3D'false', deviceAlias=3D'channel0', customProperties=3D'[]', snapshotId=3D'null', logicalName=3D'null', hostDevice=3D'null'}}, vmType=3Dkvm, = memSize=3D2048, smpCoresPerSocket=3D1, vmName=3DVM-RIRI, nice=3D0, status=3DUp, = maxMemSize=3D8192, bootMenuEnable=3Dtrue, vmId=3Dc6c3f049-ae61-4227-839e-9f70d29e910b, smpThreadsPerCore=3D1, guestDiskMapping=3D{}, maxMemSlots=3D16, = kvmEnable=3Dtrue, displayNetwork=3Dovirtmgmt, devices=3D[Ljava.lang.Object;@2e2fc0fa, = maxVCpus=3D16, clientIp=3D, statusTime=3D4372160030, display=3Dqxl}], log id: = 7d4624e8<o:p></o:p> 2017-06-13 16:46:23,146+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmDevicesMonitoring] (ForkJoinPool-1-worker-13) [] Received a spice Device without an address = when processing VM c6c3f049-ae61-4227-839e-9f70d29e910b devices, skipping = device: {device=3Dspice, specParams=3D{fileTransferEnable=3Dtrue, = displayNetwork=3Dovirtmgmt, spiceSecureChannels=3Dsmain,sinputs,scursor,splayback,srecord,sdisplay,ss= martcard,susbredir, displayIp=3D172.17.74.216, copyPasteEnable=3Dtrue}, type=3Dgraphics, deviceId=3D84364ae9-1984-4d24-bc5b-aa3969502205, = tlsPort=3D5900}<o:p></o:p> 2017-06-13 16:46:23,244+02 INFO  [org.ovirt.engine.core.bll.VmSlaPolicyCommand] (org.ovirt.thread.pool-6-thread-38) [6ab21bc6] Running command: VmSlaPolicyCommand internal: true. Entities affected :  ID: c6c3f049-ae61-4227-839e-9f70d29e910b Type: VMAction group = EDIT_VM_PROPERTIES with role type USER<o:p></o:p> 2017-06-13 16:46:23,245+02 INFO  [org.ovirt.engine.core.vdsbroker.UpdateVmPolicyVDSCommand] (org.ovirt.thread.pool-6-thread-38) [6ab21bc6] START, UpdateVmPolicyVDSCommand(HostName =3D RIRI, UpdateVmPolicyVDSParams:{runAsync=3D'true', hostId=3D'87e118d8-5331-4b5e-8fd1-c5e7ef91e687', vmId=3D'c6c3f049-ae61-4227-839e-9f70d29e910b'}), log id: = 12ae92d2<o:p></o:p> 2017-06-13 16:46:24,250+02 INFO  = [org.ovirt.engine.core.vdsbroker.UpdateVmPolicyVDSCommand] (org.ovirt.thread.pool-6-thread-38) [6ab21bc6] FINISH, UpdateVmPolicyVDSCommand, log id: 12ae92d2<o:p></o:p> 2017-06-13 16:46:24,326+02 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] = (org.ovirt.thread.pool-6-thread-38) [6ab21bc6] EVENT_ID: VM_SLA_POLICY_CPU(10,550), Correlation ID: = 6ab21bc6, Call Stack: null, Custom Event ID: -1, Message: VM VM-RIRI SLA Policy was = set. CPU limit is set to 10<o:p></o:p> 2017-06-13 16:46:29,942+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler4) [] VM 'c6c3f049-ae61-4227-839e-9f70d29e910b' = was reported as Down on VDS = 'f5523fc0-be7b-4097-a987-bc1902acab84'(fifi)<o:p></o:p>= 2017-06-13 16:46:29,943+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (DefaultQuartzScheduler4) [] START, DestroyVDSCommand(HostName =3D fifi, DestroyVmVDSCommandParameters:{runAsync=3D'true', hostId=3D'f5523fc0-be7b-4097-a987-bc1902acab84', vmId=3D'c6c3f049-ae61-4227-839e-9f70d29e910b', force=3D'false', = secondsToWait=3D'0', gracefully=3D'false', reason=3D'', ignoreNoVm=3D'true'}), log id: = 4666101e<o:p></o:p> 2017-06-13 16:46:31,175+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (DefaultQuartzScheduler4) [] FINISH, DestroyVDSCommand, log id: = 4666101e<o:p></o:p> 2017-06-13 16:46:31,175+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler4) [] VM = 'c6c3f049-ae61-4227-839e-9f70d29e910b'(VM-RIRI) was unexpectedly detected as 'Down' on VDS 'f5523fc0-be7b-4097-a987-bc1902acab84'(fifi) (expected on '87e118d8-5331-4b5e-8fd1-c5e7ef91e687')<o:p></o:p> 2017-06-13 16:46:48,001+02 INFO  [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] (DefaultQuartzScheduler2) [] Fetched 2 VMs from VDS 'f5523fc0-be7b-4097-a987-bc1902acab84'<o:p></o:p> </div> </body> </html> ------=_NextPart_000_003D_01D2E468.6B6F3E70--

1 0

Need Support - Engine VM Down
by Rizwan Qureshi 13 Jun '17

13 Jun '17

--_000_LOXP123MB1061A1A528C9064B12F847CCEDCD0LOXP123MB1061GBRP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Developers, We are new to ovirt. We unfortunately managed to break our oVirt installati= on. The engine VM does not seem to start after we updated to 4.0 from 3.6 a= nd did a restart. We are looking for someone specialized to fix this kind of issues. I have f= ailed to find anyone who provides support for oVirt so resorting to the use= rs list now. Already tried using the users list and someone did try to help= but could not get it to work. You can see the thread below for reference a= nd logs that I posted: http://lists.ovirt.org/pipermail/users/2017-May/082309.html Can anyone help please? -- Best Regards, Rizwan Qureshi VoIP Admin Ph: 01482427836 --_000_LOXP123MB1061A1A528C9064B12F847CCEDCD0LOXP123MB1061GBRP_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> Hello Developers,<o:p></o:p> We are new to ovirt. We unfortunately managed to bre= ak our oVirt installation. The engine VM does not seem to start after we up= dated to 4.0 from 3.6 and did a restart.<o:p></o:p> <o:p> </o:p> We are looking for someone specialized to fix this k= ind of issues. I have failed to find anyone who provides support for oVirt = so resorting to the users list now. Already tried using the users list and = someone did try to help but could not get it to work. You can see the thread below for reference and logs th= at I posted:<o:p></o:p> <o:p> </o:p> <a href=3D"http://lists.ovirt.org/pipermail/users/20= 17-May/082309.html">http://lists.ovirt.org/pipermail/users/2017-May/082309.= html</a><o:p></o:p> <o:p> </o:p> Can anyone help please?<o:p></o:p> <o:p> </o:p> <o:p> </o:p> --<o:p></o:p> Best Regards,<o:p></o:p>= Rizwan Qureshi<o:p></o:p></span= > VoIP Admin<o:p></o:p></p= > Ph: 01482427836<o:p></o:p></spa= n> <o:p> </o:p> </div> </body> </html> --_000_LOXP123MB1061A1A528C9064B12F847CCEDCD0LOXP123MB1061GBRP_--

2 1

Host name already in use in oVirt Engine
by FERNANDO FREDIANI 13 Jun '17

13 Jun '17

This is a multi-part message in MIME format. --------------3A9AA83C242C9D0BB163DB52 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello. I had a previous Datacenter and Cluster with a Host in it which I have removed completelly from oVirt Engine. In order to remove I did the following steps: - Removed all Virtual Machines on the top of the Host - Put the only Local Datastore in Maintenence mode (It didn't allow to remove it for some reason. Said I had to remove the Datacenter instead) - As the Datastore couldn't be remove so the Host. I then removed the Datacenter and it removed everything. Then I created a new Cluster and tried to add the same Host with the same hostname in it and I am getting the message: "Cannot add Host. The Host name is already in use, please choose a unique name and try again." It seems that something was left lost in the Database which still beleives that host exists in oVirt Engine. How can I clean that up and add it again as I am not willing to change its name. Thanks Fernand --------------3A9AA83C242C9D0BB163DB52 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hello. I had a previous Datacenter and Cluster with a Host in it which I have removed completelly from oVirt Engine. In order to remove I did the following steps: - Removed all Virtual Machines on the top of the Host - Put the only Local Datastore in Maintenence mode (It didn't allow to remove it for some reason. Said I had to remove the Datacenter instead) - As the Datastore couldn't be remove so the Host. I then removed the Datacenter and it removed everything. Then I created a new Cluster and tried to add the same Host with the same hostname in it and I am getting the message: "Cannot add Host. The Host name is already in use, please choose a unique name and try again." It seems that something was left lost in the Database which still beleives that host exists in oVirt Engine. How can I clean that up and add it again as I am not willing to change its name. Thanks Fernand </body> </html> --------------3A9AA83C242C9D0BB163DB52--

1 1

SPM in case of Failure
by Arsène Gschwind 13 Jun '17

13 Jun '17

This is a multi-part message in MIME format. --------------2697A26DEF0A6FEBE4ECD7F9 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi Our setup looks like: - 2 clusters in 2 different site connected with 10GBit LAN - Storage based on FC SAN replicated on both site and available for both site (The LUNs are available over 4 pathes, 2 from each site) My observation: In case one site goes down and this site owned SPM is it not possible to move or force SPM on the second site. On the site which is down it's possible to reset all VMs that crashed using the "Confirm Host rebooted" menu on the oVirt Host but this does not reset SPM. The only solution I found was to bring the Host which owned SPM up again to be able to move it to the other site and then reactivate the storage domains. Is this a normal behavior? Is there any way to force SPM reelection ? Thanks for your help or idea... Regards, Arsène -- *Arsène Gschwind* Fa. Sapify AG im Auftrag der Universität Basel IT Services Klingelbergstr. 70 | CH-4056 Basel | Switzerland Tel. +41 79 449 25 63 | http://its.unibas.ch <http://its.unibas.ch/> ITS-ServiceDesk: support-its(a)unibas.ch | +41 61 267 14 11 --------------2697A26DEF0A6FEBE4ECD7F9 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi Our setup looks like: - 2 clusters in 2 different site connected with 10GBit LAN - Storage based on FC SAN replicated on both site and available for both site (The LUNs are available over 4 pathes, 2 from each site) My observation: In case one site goes down and this site owned SPM is it not possible to move or force SPM on the second site. On the site which is down it's possible to reset all VMs that crashed using the "Confirm Host rebooted" menu on the oVirt Host but this does not reset SPM. The only solution I found was to bring the Host which owned SPM up again to be able to move it to the other site and then reactivate the storage domains. Is this a normal behavior? Is there any way to force SPM reelection ? Thanks for your help or idea... Regards, Arsène <div class="moz-signature">-- Arsène Gschwind Fa. Sapify AG im Auftrag der Universität Basel IT Services Klingelbergstr. 70 | CH-4056 Basel | Switzerland Tel. +41 79 449 25 63 | <a href="http://its.unibas.ch/"> http://its.unibas.ch </a> ITS-ServiceDesk: <a class="moz-txt-link-abbreviated" href="mailto:support-its@unibas.ch">support-its(a)unibas.ch</a> | +41 61 267 14 11 </div> </body> </html> --------------2697A26DEF0A6FEBE4ECD7F9--

2 1

Python-SDK4: Managing accents?
by nicolas＠devels.es 13 Jun '17

13 Jun '17

Hi, We're running Python SDK (ovirt-engine-sdk-python) ver 4.1.4 and we're having some issues getting values that contain accents. For example, this snippet fails: import ovirtsdk4 as sdk import ovirtsdk4.types as types # Create the connection to the server: connection = sdk.Connection( url='https://fqdn/ovirt-engine/api', username='...', password='...', ca_file='...', debug=True, ) users_service = connection.system_service().users_service() users = users_service.list() connection.close() This snippet fails in the "users = users_service.list()" line, because one of the records have a tilde (ó). The trace is: Traceback (most recent call last): File "lista_users", line 23, in <module> users = users_service.list() File "/home/ovirt/prueba/ejemplo2/lib/python2.7/site-packages/ovirtsdk4/services.py", line 22155, in list return self._internal_get(headers, query, wait) File "/home/ovirt/prueba/ejemplo2/lib/python2.7/site-packages/ovirtsdk4/service.py", line 202, in _internal_get return future.wait() if wait else future File "/home/ovirt/prueba/ejemplo2/lib/python2.7/site-packages/ovirtsdk4/service.py", line 53, in wait return self._code(response) File "/home/ovirt/prueba/ejemplo2/lib/python2.7/site-packages/ovirtsdk4/service.py", line 197, in callback return self._internal_read_body(response) File "/home/ovirt/prueba/ejemplo2/lib/python2.7/site-packages/ovirtsdk4/service.py", line 310, in _internal_read_body return reader.Reader.read(response.body) File "/home/ovirt/prueba/ejemplo2/lib/python2.7/site-packages/ovirtsdk4/reader.py", line 297, in read cursor = xml.XmlReader(io.BytesIO(source.encode('utf-8'))) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 1899: ordinal not in range(128) Opening the source code (ovirtsdk4/reader.py) file and seeking the exact line that fails I can see: if isinstance(source, str): cursor = xml.XmlReader(io.BytesIO(source.encode('utf-8'))) If I add a line just after the 'if' being "cursor = cursor.decode('utf-8')", it seems to work, but I guess the source code should handle this kind of situations. Is this a known issue? Should I open a BZ? Any workaround meanwhile? Thanks.

3 4

Question about Clusters and Storage usage
by FERNANDO FREDIANI 13 Jun '17

13 Jun '17

This is a multi-part message in MIME format. --------------AF09066F7B7B6BE6AE98327E Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello folks. I have here a scenario where I have one Datacenter and inside it I have one Cluster which has multiple hosts with Shared storage between them. Now I am willing to add another standalone host with Local Storage only and logic tells me to add to the same Datacenter created as they are in fact in the same physical Datacenter, but as this host has only Local Storage I shouldn't obviously add to the existing cluster. Question is: As the Datacenter was created with Storage type Shared - Should I create a new Cluster and add it to it, even though the new Host has only Local Storage - Or should I create another Datacenter with Storage Type Local, a cluster within it and then add the Host there ? Thanks Fernando --------------AF09066F7B7B6BE6AE98327E Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hello folks. I have here a scenario where I have one Datacenter and inside it I have one Cluster which has multiple hosts with Shared storage between them. Now I am willing to add another standalone host with Local Storage only and logic tells me to add to the same Datacenter created as they are in fact in the same physical Datacenter, but as this host has only Local Storage I shouldn't obviously add to the existing cluster. Question is: As the Datacenter was created with Storage type Shared - Should I create a new Cluster and add it to it, even though the new Host has only Local Storage - Or should I create another Datacenter with Storage Type Local, a cluster within it and then add the Host there ? Thanks Fernando </body> </html> --------------AF09066F7B7B6BE6AE98327E--

2 1

Re: [ovirt-users] Migrating oVirt cluster from 4.0 to 4.1
by Karli Sjöberg 12 Jun '17

12 Jun '17

3 2

Re: [ovirt-users] hosted-engine network
by Arsène Gschwind 12 Jun '17

12 Jun '17

Hi, Sorry for this, it seems that the attachment have been detached. So let's try again Regards, Arsène On 06/12/2017 11:59 AM, Martin Sivak wrote: > Hi, > > I would love to help you, but I didn't get the log file.. > > Regards > > Martin Sivak > > On Mon, Jun 12, 2017 at 11:49 AM, Arsène Gschwind > <arsene.gschwind(a)unibas.ch> wrote: >> Hi all, >> >> Any chance to get help or a hint to solve my Problem, I have no idea how to >> change this configuration since it is not possible using the WebUI. >> >> Thanks a lot. >> >> Regards, >> Arsène >> >> >> On 06/07/2017 11:50 AM, Arsène Gschwind wrote: >> >> Hi all, >> >> Please find attached the agent.log DEBUG and a screenshot from webui >> >> Thanks a lot >> >> Best regards, >> >> Arsène >> >> >> On 06/07/2017 11:27 AM, Martin Sivak wrote: >> >> Hi all, >> >> Yanir is right, the local vm.conf is just a cache of what was >> retrieved from the engine. >> >> I might be interesting to check what the configuration of the engine >> VM shows when edited using the webadmin. Or enable debug logging [1] >> for hosted engine and add the OVF dump we send there now and then (the >> xml representation of the VM). >> >> [1] See /etc/ovirt-hosted-engine-ha/agent-log.conf and change the >> level for root logger to DEBUG >> >> Best regards >> >> Martin Sivak >> >> On Wed, Jun 7, 2017 at 11:12 AM, Yanir Quinn <yquinn(a)redhat.com> wrote: >> >> If im not mistaken the values of vm.conf are repopulated from the database , >> but i wouldn't recommend meddling with DB data. >> maybe the network device wasn't set properly during the hosted engine setup >> ? >> >> On Wed, Jun 7, 2017 at 11:47 AM, Arsène Gschwind <arsene.gschwind(a)unibas.ch> >> wrote: >> >> Hi, >> >> Any chance to get a hint how to change the vm.conf file so it will not be >> overwritten constantly? >> >> Thanks a lot. >> >> Arsène >> >> >> On 06/06/2017 09:50 AM, Arsène Gschwind wrote: >> >> Hi, >> >> I've migrated our oVirt engine to hosted-engine located on a FC storage >> LUN, so far so good. >> For some reason I'm not able to start the hosted-engine VM, after digging >> in the log files i could figured out the reason. The Network device was set >> to "None" as follow: >> >> devices={nicModel:pv,macAddr:00:16:3e:3a:6b:60,linkActive:true,network:None,deviceId:56cb4d71-13ff-42a8-bb83-7faef99fd3ea,address:{slot:0x03,bus:0x00,domain:0x0000,type:pci,function:0x0},device:bridge,type:interface} >> >> I've created a new config file /var/run/ovirt-hosted-engine-ha/vm.conf.new >> and set the nic device to ovirtmgnt, the I could start the hosted-engine >> using : >> hosted-engine --vm-start >> --vm-conf=var/run/ovirt-hosted-engine-ha/vm.conf.new >> >> The nic device line in vm.conf.new looks like: >> >> devices={nicModel:pv,macAddr:00:16:3e:3a:6b:60,linkActive:true,network:ovirtmgmt,deviceId:56cb4d71-13ff-42a8-bb83-7faef99fd3ea,address:{slot:0x03,bus:0x00,domain:0x0000,type:pci,function:0x0},device:bridge,type:interface} >> >> I tried to find out a way to change this setting on vm.conf but it is >> constantly rewritten, even when using the webui is say's: >> HostedEngine: >> >> There was an attempt to change Hosted Engine VM values that are locked. >> >> Is there a way to modify/correct the hosted-engine vm.conf file so it will >> stay and not be overwritten? >> >> Thanks a lot for any hint/help >> >> rgds, >> arsène >> >> -- >> >> Arsène Gschwind >> Fa. Sapify AG im Auftrag der Universität Basel >> IT Services >> Klingelbergstr. 70 | CH-4056 Basel | Switzerland >> Tel. +41 79 449 25 63 | http://its.unibas.ch >> ITS-ServiceDesk: support-its(a)unibas.ch | +41 61 267 14 11 >> >> >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> >> -- >> >> Arsène Gschwind >> Fa. Sapify AG im Auftrag der Universität Basel >> IT Services >> Klingelbergstr. 70 | CH-4056 Basel | Switzerland >> Tel. +41 79 449 25 63 | http://its.unibas.ch >> ITS-ServiceDesk: support-its(a)unibas.ch | +41 61 267 14 11 >> >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> >> -- >> >> Arsène Gschwind >> Fa. Sapify AG im Auftrag der Universität Basel >> IT Services >> Klingelbergstr. 70 | CH-4056 Basel | Switzerland >> Tel. +41 79 449 25 63 | http://its.unibas.ch >> ITS-ServiceDesk: support-its(a)unibas.ch | +41 61 267 14 11 >> >> >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> >> -- >> >> Arsène Gschwind >> Fa. Sapify AG im Auftrag der Universität Basel >> IT Services >> Klingelbergstr. 70 | CH-4056 Basel | Switzerland >> Tel. +41 79 449 25 63 | http://its.unibas.ch >> ITS-ServiceDesk: support-its(a)unibas.ch | +41 61 267 14 11 >> >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> -- *Arsène Gschwind* Fa. Sapify AG im Auftrag der Universität Basel IT Services Klingelbergstr. 70 | CH-4056 Basel | Switzerland Tel. +41 79 449 25 63 | http://its.unibas.ch <http://its.unibas.ch/> ITS-ServiceDesk: support-its(a)unibas.ch | +41 61 267 14 11

1 0

hosted-engine network
by Arsène Gschwind 12 Jun '17

12 Jun '17

This is a multi-part message in MIME format. --------------DDB6A5C853028C92A7A2BFFF Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi, I've migrated our oVirt engine to hosted-engine located on a FC storage LUN, so far so good. For some reason I'm not able to start the hosted-engine VM, after digging in the log files i could figured out the reason. The Network device was set to "None" as follow: devices={nicModel:pv,macAddr:00:16:3e:3a:6b:60,linkActive:true,network:*None*,deviceId:56cb4d71-13ff-42a8-bb83-7faef99fd3ea,address:{slot:0x03,bus:0x00,domain:0x0000,type:pci,function:0x0},device:bridge,type:interface} I've created a new config file /var/run/ovirt-hosted-engine-ha/vm.conf.new and set the nic device to ovirtmgnt, the I could start the hosted-engine using : hosted-engine --vm-start --vm-conf=var/run/ovirt-hosted-engine-ha/vm.conf.new The nic device line in vm.conf.new looks like: devices={nicModel:pv,macAddr:00:16:3e:3a:6b:60,linkActive:true,network:*ovirtmgmt*,deviceId:56cb4d71-13ff-42a8-bb83-7faef99fd3ea,address:{slot:0x03,bus:0x00,domain:0x0000,type:pci,function:0x0},device:bridge,type:interface} I tried to find out a way to change this setting on vm.conf but it is constantly rewritten, even when using the webui is say's: HostedEngine: * There was an attempt to change Hosted Engine VM values that are locked. Is there a way to modify/correct the hosted-engine vm.conf file so it will stay and not be overwritten? Thanks a lot for any hint/help rgds, arsène -- *Arsène Gschwind* Fa. Sapify AG im Auftrag der Universität Basel IT Services Klingelbergstr. 70 | CH-4056 Basel | Switzerland Tel. +41 79 449 25 63 | http://its.unibas.ch <http://its.unibas.ch/> ITS-ServiceDesk: support-its(a)unibas.ch | +41 61 267 14 11 --------------DDB6A5C853028C92A7A2BFFF Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi, I've migrated our oVirt engine to hosted-engine located on a FC storage LUN, so far so good. For some reason I'm not able to start the hosted-engine VM, after digging in the log files i could figured out the reason. The Network device was set to "None" as follow: devices={nicModel:pv,macAddr:00:16:3e:3a:6b:60,linkActive:true,network:None,deviceId:56cb4d71-13ff-42a8-bb83-7faef99fd3ea,address:{slot:0x03,bus:0x00,domain:0x0000,type:pci,function:0x0},device:bridge,type:interface} I've created a new config file /var/run/ovirt-hosted-engine-ha/vm.conf.new and set the nic device to ovirtmgnt, the I could start the hosted-engine using : hosted-engine --vm-start --vm-conf=var/run/ovirt-hosted-engine-ha/vm.conf.new The nic device line in vm.conf.new looks like: devices={nicModel:pv,macAddr:00:16:3e:3a:6b:60,linkActive:true,network:ovirtmgmt,deviceId:56cb4d71-13ff-42a8-bb83-7faef99fd3ea,address:{slot:0x03,bus:0x00,domain:0x0000,type:pci,function:0x0},device:bridge,type:interface} I tried to find out a way to change this setting on vm.conf but it is constantly rewritten, even when using the webui is say's: <span style="color: rgb(0, 0, 0); font-family: "Arial Unicode MS", Arial, sans-serif; font-size: small; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">HostedEngine: <ul style="box-sizing: border-box; margin-top: 0px; margin-bottom: 10px; color: rgb(0, 0, 0); font-family: "Arial Unicode MS", Arial, sans-serif; font-size: small; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial;"> <li style="box-sizing: border-box;">There was an attempt to change Hosted Engine VM values that are locked.</li> </ul> Is there a way to modify/correct the hosted-engine vm.conf file so it will stay and not be overwritten? Thanks a lot for any hint/help rgds, arsène <div class="moz-signature">-- Arsène Gschwind Fa. Sapify AG im Auftrag der Universität Basel IT Services Klingelbergstr. 70 | CH-4056 Basel | Switzerland Tel. +41 79 449 25 63 | <a href="http://its.unibas.ch/"> http://its.unibas.ch </a> ITS-ServiceDesk: <a class="moz-txt-link-abbreviated" href="mailto:support-its@unibas.ch">support-its(a)unibas.ch</a> | +41 61 267 14 11 </div> </body> </html> --------------DDB6A5C853028C92A7A2BFFF--

3 6

trouble when creating VM snapshots including memory
by Matthias Leopold 12 Jun '17

12 Jun '17

hi, i'm having trouble creating VM snapshots that include memory in my oVirt 4.1 test environment. when i do this the VM gets paused and shortly (20-30s) afterwards i'm seeing messages in engine.log about both iSCSI storage domains (master storage domain and data storage where VM resides) experiencing high latency. this quickly worsens from the engines view: VM is unresponsive, Host is unresponsive, engine wants to fence the host (impossible because it's the only host in the test cluster). in the end there is an EngineException EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetworkException: Message timeout which can be caused by communication issues (Failed with error VDS_NETWORK_ERROR and code 5022) the snapshot fails and is left in an inconsistent state. the situation has to be resolved manually with unlock_entity.sh and maybe lvm commands. this happened twice in exactly the same manner. VM snapshots without memory for this VM are not a problem. VM guest OS is CentOS7 installed from one of the ovirt-image-repository images. it has the oVirt guest agent running. what could be wrong? this is a test environment where lots of parameters aren't optimal but i never had problems like this before, nothing concerning network latency. iSCSI is on a FreeNAS box. CPU, RAM, ethernet (10GBit for storage) on all hosts involved (engine hosted externally, oVirt Node, storage) should be OK by far. it looks like some obvious configuration botch or performance bottleneck to me. can it be linked to the network roles (management and migration network are on a 1 GBit link)? i'm still new to this, not a lot of KVM experience, too. maybe someone recognizes the culprit... thx matthias

2 2

Re: [ovirt-users] trouble when creating VM snapshots including memory
by Karli Sjöberg 12 Jun '17

12 Jun '17

2 1

Re-adding oVirt host.
by Marcin M. Jessa 12 Jun '17

12 Jun '17

Hi guys. I have a two node setup. One server running on CentOS [1] and one server with oVirt node [2]. I added local storage to my oVirt host but I forgot the storage I chose was already in use so it failed. I then got a host entry with local storage which was shown as not configured. I then removed that local storage host but then it completely disappeared from my setup. Then I tried to add it again but oVirt said that host is already defined. I tried different name with the same IP but it also failed saying that that IP is already defined. Is there a way to re-add that previously defined host? How can I bring it back? [1]: oVirt Engine Version: 4.1.2.2-1.el7.centos [2]: oVirt Node 4.1.2 Marcin Jessa.

3 2

chrony or ntp ?
by Fabrice Bacchella 11 Jun '17

11 Jun '17

I haven't switched from ntp to chrony. So I have configured my puppet to remove it as it's now part of default installation of rhel. I works well with everything except on vdsm, since last upgrade: # yum erase chrony .. Removing for dependencies: vdsm x86_64 4.19.15-1.el7.centos @ovirt-4.1 2.6 M vdsm-hook-vmfex-dev noarch 4.19.15-1.el7.centos @ovirt-4.1 21 k Why vdsm depends on chrony ? Any time synchronisation solution is good. Is that the role of ovirt to chose for me ?

4 8

Hardware for Hyperconverged oVirt: Gluster storage best practice
by ovirt＠fateknollogee.com 11 Jun '17

11 Jun '17

Martin, Looking to test oVirt on real hardware (aka no nesting) Scenario # 1: 1x Supermicro 2027TR-HTRF 2U 4 node server I will install the o/s for each node on a SATADOM. Since each node will have 6x SSD for gluster storage. Should this be software RAID, hardware RAID or no RAID? Scenario # 2: 3x SuperMicro SC216E16-R1200LPB 2U server Each server has 24x 2.5" bays (front) + 2x 2.5" bays (rear) I will install the o/s on the drives using the rear bays (maybe RAID 1?) For Gluster, we will use the 24 front bays. Should this be software RAID, hardware RAID or no RAID? Thanks Femi

4 8

Re: [ovirt-users] Hardware for Hyperconverged oVirt: Gluster storage best practice
by Karli Sjöberg 11 Jun '17

11 Jun '17

1 0

ovirt client developpement
by Fabrice Bacchella 11 Jun '17

11 Jun '17

For my ovirt cli, I would like to have unit tests. But there is nothing to test in standalone mode, I need a running ovirt with a database in a known state. Is there some where a docker images with a toy setup, or a mock ovirt engine that can be downloaded and used for that ?

3 3

Can't access ovirt-engine webpage
by Thomas Wakefield 11 Jun '17

11 Jun '17

After a reboot I can’t access the management ovirt-engine webpage anymore. server.log line that looks bad: 2017-06-04 21:35:55,652-04 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0190: Step handler org.jboss.as.server.deployment.DeploymentHandlerUtil$5@61b686ed for operation {"operation" => "undeploy","address" => [("deployment" => "engine.ear")],"owner" => [("subsystem" => "deployment-scanner"),("scanner" => "default")]} at address [("deployment" => "engine.ear")] failed handling operation rollback -- java.lang.IllegalStateException: WFLYCTL0345: Timeout after 5 seconds waiting for existing service service jboss.deployment.unit."engine.ear".contents to be removed so a new instance can be installed.: java.lang.IllegalStateException: WFLYCTL0345: Timeout after 5 seconds waiting for existing service service jboss.deployment.unit."engine.ear".contents to be removed so a new instance can be installed. at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:2107) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.server.deployment.PathContentServitor.addService(PathContentServitor.java:50) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.server.deployment.DeploymentHandlerUtil.doDeploy(DeploymentHandlerUtil.java:165) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.server.deployment.DeploymentHandlerUtil$5$1.handleResult(DeploymentHandlerUtil.java:333) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1384) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1366) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1328) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1311) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1185) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:767) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:644) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1329) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:400) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:222) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.controller.ModelControllerImpl$3$1$1.run(ModelControllerImpl.java:756) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at org.jboss.as.controller.ModelControllerImpl$3$1$1.run(ModelControllerImpl.java:750) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_131] at org.jboss.as.controller.ModelControllerImpl$3$1.run(ModelControllerImpl.java:750) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_131] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_131] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [rt.jar:1.8.0_131] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [rt.jar:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131] at org.jboss.threads.JBossThread.run(JBossThread.java:320) [jboss-threads-2.2.1.Final.jar:2.2.1.Final] 2017-06-04 21:36:00,654-04 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0349: Timeout after [5] seconds waiting for service container stability while finalizing an operation. Process must be restarted. Step that first updated the service container was 'undeploy' at address '[("deployment" => "engine.ear")]' 2017-06-04 21:36:00,655-04 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."engine.ear"."bll.jar".component.InitBackendServicesOnStartupBean.START Similar issue in engine.log: 2017-06-04 21:30:50,076-04 ERROR [org.ovirt.engine.core.bll.InitBackendServicesOnStartupBean] (ServerService Thread Pool -- 40) [38484164] Failed to initialize backend: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private void org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.init() on org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller@438212cb at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:70) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:189) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:100) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.ovirt.engine.core.bll.ServiceLoader.load(ServiceLoader.java:34) [bll.jar:] at org.ovirt.engine.core.bll.InitBackendServicesOnStartupBean.create(InitBackendServicesOnStartupBean.java:65) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_131] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_131] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_131] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_131] at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doLifecycleInterception(Jsr299BindingsInterceptor.java:114) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:103) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:53) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:349) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.singleton.StartupCountDownInterceptor.processInvocation(StartupCountDownInterceptor.java:25) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:124) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:138) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_131] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131] at org.jboss.threads.JBossThread.run(JBossThread.java:320) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_131] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_131] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_131] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_131] at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:98) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] ... 64 more Caused by: java.lang.NullPointerException at org.ovirt.engine.core.bll.storage.disk.image.BaseImagesCommand.isDataOperationsByHSM(BaseImagesCommand.java:128) [bll.jar:] at org.ovirt.engine.core.bll.storage.disk.image.CopyImageGroupCommand.isUsingSPDMFlow(CopyImageGroupCommand.java:105) [bll.jar:] at org.ovirt.engine.core.bll.storage.disk.image.CopyImageGroupCommand.getCallback(CopyImageGroupCommand.java:188) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandsRepository.addToCallbackMap(CommandsRepository.java:69) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.initCommandExecutor(CommandCallbacksPoller.java:191) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.init(CommandCallbacksPoller.java:41) [bll.jar:] ... 69 more

2 4

Cannnot change display resolution using spice
by Станислав Ефремов 10 Jun '17

10 Jun '17

This is a multipart message in MIME format. ------=_NextPart_000_01A1_01D2E0FD.73774630 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I`m using CentOS Linux release 7.3.1611 and oVirt 4.1.2 =20 I`m testing oVirt to use it like vdi solution. I cannot change = resolution everywhere, except Fedora 25 with Gnome3 and GDM.=20 In others distro display resolution setting 1024x768 and might be set to = 800x600. Xrandr shows all available modes but when I set resolution its failed = and I cannot interact with desktop except ctrl-alt-f1.=20 Can it related to vgamem? =20 ------=_NextPart_000_01A1_01D2E0FD.73774630 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta = http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta = name=3DGenerator content=3D"Microsoft Word 15 (filtered = medium)"><style></style></head><body lang=3DRU = link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1>I`m using CentOS Linux release = 7.3.1611 and oVirt 4.1.2<o:p></o:p><o:p> </o:p>I`m testing oVirt to use it like vdi solution. I cannot = change resolution everywhere, except Fedora 25 with Gnome3 and GDM. = <o:p></o:p>In others = distro display resolution setting 1024x768 and might be set to = 800x600.<o:p></o:p>Xrandr shows all available modes but when I set resolution = its failed and I cannot interact with desktop except ctrl-alt-f1. = <o:p></o:p>Can it = related to vgamem?<o:p></o:p><o:p> </o:p></div></body></html> ------=_NextPart_000_01A1_01D2E0FD.73774630--

2 2

nfs.home.lan already exits with uuid
by Greg Fitzgerald 10 Jun '17

10 Jun '17

Hi, I just replaced my local proxmox server with ovirt for some testing. When I woke up this morning one of my VM's nfs.home.lan was offline. So I tried to power it back on and I received following event message. VM nfs.home.lan is down with error. Exit message: operation failed: domain 'nfs.home.lan' already exists with uuid b6453519-4124-4a47-9fb8-064be743067d. I tried to reboot the physical machine, I also tried destroying the VM (keeping the disk drives) and recreating it and attaching the drive again. Always end up with the same error message. Best Regards, Greg Fitzgerald

1 0

Hosted-Engine --Deploy option in Web
by Langley, Robert 10 Jun '17

10 Jun '17

--_000_MWHPR09MB1421B9141F477FFABB427B6587CE0MWHPR09MB1421namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable There is no Hosted Engine option within the Edit window of my additional ho= st. How do I deploy Hosted-Engine to an existing host, if I've forgotten to= do so when adding it as a new host? And, this host is one of the three sto= rage servers hosting the engine gluster volume. Thanks, Robert Langley --_000_MWHPR09MB1421B9141F477FFABB427B6587CE0MWHPR09MB1421namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Exchange Server">  <style></style> </head> <body> <div>There is no Hosted Engine option within the Edit window of my addition= al host. How do I deploy Hosted-Engine to an existing host, if I’ve f= orgotten to do so when adding it as a new host? And, this host is one of th= e three storage servers hosting the engine gluster volume.</div> <div> </div> <div>Thanks,</div> <div>Robert Langley</div> <div> </div> </body> </html> --_000_MWHPR09MB1421B9141F477FFABB427B6587CE0MWHPR09MB1421namp_--

2 1

Building oVirt engine on Debian
by Leni Kadali Mutungi 10 Jun '17

10 Jun '17

Ran `make clean install-dev` and the process freezes at: [INFO] weaveinfo Join point 'constructor-execution(void com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.<init>(com.google.gwt.dev.jjs.ast.JProgram))' in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer' (ControlFlowAnalyzer.java:905) advised by after advice from 'org.ovirt.engine.ui.gwtaop.DontPrune' (DontPrune.java) My computer freezes at that point and I have to power it off. I tried doing it in the terminal without the Desktop Environment and I get the same result. The component being built is the UI Common Web. Advice on what to do next is appreciated. -- - Warm regards Leni Kadali Mutungi

2 18

Re: [ovirt-users] unsuccessful hosted engine install
by Sandro Bonazzola 09 Jun '17

09 Jun '17

On Wed, May 31, 2017 at 4:45 AM, Brendan Hartzell <mrrex4(a)gmail.com> wrote: > Can you please elaborate about the failure you see here and how are you > trying to manually partition the host? > > Sure, I will start from the beginning. > - Using: ovirt-node-ng-installer-ovirt-4.1-2017052604 <(201)%20705-2604> > .iso > - During installation I setup one of the two interfaces and check the box > to automatically use the connection. > - I'm currently providing a host name of node-1.test.net until I have a > successful process. > - I configure date and time for my timezone and to use an internal NTP > server. > - On Installation Destination, I pick my 128GB USB3.0 SanDisk flash drive, > check the box that I would like to make additional space, and click done. > In the reclaim disk space window, I click delete all, and then reclaim > space. I go back into the Installation Destination, select that I will > configure partitioning, and click done. The Manual Partitioning window > opens, I use the option to automatically create mount points. > In this screen, please change partitioning scheme from LVM to LVM Thin Provisioning: it should solve your following error. > At this point, /boot is 1024MB, /var is 15GB, / is 88.11 GB, and swap is > 11.57GB. I then change / to 23.11 GB, update settings, change /var to > 80GB, update settings again, and click done. I accept the changes and > begin installation. > > I tried these changes based on this article: http://www.ovirt.org/ > documentation/self-hosted/chap-Deploying_Self-Hosted_Engine/ > > The article does say that you can specify a different directory than > /var/tmp, but I don't recall seeing that option. > If the setup detects not enough space in /var/tmp for extracting the appliance it will ask about a different directory. > > After some time, I get the following error: > There was an error running the kickstart script at line 7. This is a > fatal error and installation will be aborted. The details of this error > are: > > [INFO] Trying to create a manageable base from '/' > [ERROR] LVM Thin Provisioning partitioning scheme is required. For > autoinstall via Kickstart with LVM Thin Provisioning check options > --thinpool and --grow. Please consult documentation for details. > ^^ this one should be solved by the LVM Thin Provisioning scheme mentioned above.. > > Traceback (most recent call last): > File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main > "__main__", fname, loader, pkg_name) > File "/usr/lib64/python2.7runpy.py", line 72, in _run_code exec code in > run_globals > File "/usr/lib/python2.7/site-packages/imgbased/__main__.py", line 51, in > <module> CliApplication() > File "/usr/lib/python2.7/site-packages/imgbased/__init__.py", line 82, in > CliApplication() > File "/usr/lib/python2.7/site-packages/imgbased/hooks.py", line 120, in > emit cb(self.context, *args) > File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line > 169, in post_argparse layout.initialize(args.source, args.init_nvr) > File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line > 216, in initialize self.app.imgbase.init_layout_from(source, init_nvr) > File "/usr/lib/python2.7/site-packages/imgbased/imgbase.py", line 271, in > init_layout_from self.init_tags_on(existing_lv) > File "/usr/lib/python2.7/site-packages/imgbased/imgbase.py", line 243, in > init_tags_on pool = lv.thinpool() > File "/usr/lib/python2.7/site-packages/imgbased/lvm.py", line 250, in > thinpool raise MissingLvmThinPool() imgbased.lvm.MissingLvmThinPool > > At this point, the only option is to exit the installer. > > **************************** > > Being this a new install, please use 4.1. oVirt 4.0 is not supported > anymore. > > Not a problem. > > **************************** > > Can you please provide hosted engine setup logs or better a full sos > report? (sosreport -a) > > Again, the process I'm following: > - Using: ovirt-node-ng-installer-ovirt-4.1-2017052604 <(201)%20705-2604> > .iso > - During installation I setup one of the two interfaces and check the box > to automatically use the connection. > - I'm currently providing a host name of node-1.test.net until I have a > successful process. > - I configure date and time for my timezone and to use an internal NTP > server. > - On Installation Destination, I pick my 128GB USB3.0 SanDisk flash drive, > check the box that I would like to make additional space, and click done. > In the reclaim disk space window, I click delete all, and then reclaim > space. > - Begin Installation and set a root password. > - Perform a yum update - no packages marked for update (as expected) > - Use vi to update /etc/hosts with a reference for node-1.test.net and > engine.test.net > - First attempt at hosted-engine from web-UI > - Setup downloads and installs ovirt-engine-appliance-4.1-20170523.1.el7. > centos.noarch.rpm > *Failed to execute stage 'Environment setup': Failed to reconfigure > libvirt for VDSM > *Hosted Engine deployment failed > - Attached SOS report > The checksum is: aa56097edc0b63c49caaf1a1fde021bc > > At this point, I would run ovirt-hosted-engine-cleanup and I would get > further along in the install process. However, because this is a fresh > install, I'm going to leave things here for now so you can review the SOS. > Thanks for the SOS report! Hosted Engine setup fails on: 2017-05-30 19:24:39 DEBUG otopi.plugins.gr_he_setup.system.vdsmenv plugin.execute:921 execute-output: ('/bin/vdsm-tool', 'configure', '--force') stdout: Checking configuration status... Current revision of multipath.conf detected, preserving lvm is configured for vdsm libvirt is already configured for vdsm SUCCESS: ssl configured to true. No conflicts Running configure... Reconfiguration of libvirt is done. 2017-05-30 19:24:39 DEBUG otopi.plugins.gr_he_setup.system.vdsmenv plugin.execute:926 execute-output: ('/bin/vdsm-tool', 'configure', '--force') stderr: Error: ServiceOperationError: _systemctlStart failed Job for libvirtd.service failed because the control process exited with error code. See "systemctl status libvirtd.service" and "journalctl -xe" for details. At the same time journalctl shows: May 30 19:24:39 node-1.test.net libvirtd[20954]: libvirt version: 2.0.0, package: 10.el7_3.5 (CentOS BuildSystem <http://bugs.centos.org>, 2017-03-03-02:09:45, c1bm.rdu2.centos.org) May 30 19:24:39 node-1.test.net libvirtd[20954]: hostname: node-1.test.net May 30 19:24:39 node-1.test.net libvirtd[20954]: The server certificate /etc/pki/vdsm/certs/vdsmcert.pem is not yet active May 30 19:24:39 node-1.test.net systemd[1]: libvirtd.service: main process exited, code=exited, status=6/NOTCONFIGURED May 30 19:24:39 node-1.test.net systemd[1]: Failed to start Virtualization daemon. May 30 19:24:39 node-1.test.net systemd[1]: Unit libvirtd.service entered failed state. May 30 19:24:39 node-1.test.net systemd[1]: libvirtd.service failed. May 30 19:24:39 node-1.test.net systemd[1]: libvirtd.service holdoff time over, scheduling restart. > > **************************** > > I'd like to understand the issues you faced before suggesting to restart > from scratch. > > Too late... I did two re-installs to get a more accurate account of my > install process for above. > > **************************** > > Thank you for your help! > > Brendan > > On Tue, May 30, 2017 at 12:17 AM, Sandro Bonazzola <sbonazzo(a)redhat.com> > wrote: > >> >> >> On Tue, May 30, 2017 at 6:49 AM, Brendan Hartzell <mrrex4(a)gmail.com> >> wrote: >> >>> oVirt users list, >>> >>> Long story short, I've been spending weeks on this project for my home >>> lab with no success. >>> >>> I would like to successfully install two nodes that host a highly >>> available engine with an iSCSI storage back-end. >>> >>> I have read through most, if not all, of the guides on ovirt.org with >>> no substantial help. >>> >>> Successfully, I have done the following: >>> Install oVirt Engine on a bare metal system, added a node, and started >>> exploring - not desired. >>> Install oVirt Node 4.0.6 on a bare metal system - fails if partitions >>> are not done automatically. >>> Install oVirt Node 4.1.2 on a bare metal system - fails if partitions >>> are not done automatically. >>> >> >> Can you please elaborate about the failure you see here and how are you >> trying to manually partition the host? >> >> >> >> >> >>> >>> My process after installing a Node: >>> Run a yum update - just to be sure, but I am using latest iso images >>> from downloads section. >>> Edit /etc/hosts for local name resolution - the goal is to host DNS as a >>> virtual machine, eventually. >>> On 4.1 if I install ovirt-engine-appliance from yum, it does simplify >>> one step in the hosted engine setup. If I do this on 4.0 it discards the >>> image and uses the default. >>> >> >> Being this a new install, please use 4.1. oVirt 4.0 is not supported >> anymore. >> >> >> >>> On 4.1 the hosted engine setup fails immediately unless I run the hosted >>> engine cleanup from the shell. >>> >> >> Can you please provide hosted engine setup logs or better a full sos >> report? (sosreport -a) >> >> >> >> >>> If I do this, I can typically get to the point of installing. >>> >>> When I do get to the installation phase, I get to a point just after >>> extracting the OVA that I get a message on the shell saying something about >>> the watchdog running the whole time and then the node reboots. >>> >>> I found one email thread that sounded like my issue and suggested the >>> following commands: >>> vdsm-tool configure --force >>> systemctl restart libvirtd >>> systemctl restart vdsmd >>> >>> Unfortunately, these commands did not help my situation like the other >>> individual. >>> >>> What log file would everyone like to see first? Given that I still >>> consider myself relatively new to Linux, please identify the path for the >>> log file requested. >>> >> >> See above >> >> >>> >>> Also, because I plan on performing a clean install for this thread using >>> my process from above (I'm not expecting my outcome to be any different), >>> are there any tips and tricks that might result in a success? >>> >> >> I'd like to understand the issues you faced before suggesting to restart >> from scratch. >> Adding some people who may help as well. >> >> >> >>> >>> Thank you for any and all help, >>> Brendan >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >>> >> >> >> -- >> >> SANDRO BONAZZOLA >> >> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D >> >> Red Hat EMEA <https://www.redhat.com/> >> <https://red.ht/sig> >> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >> > > -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

4 13

Seamless SAN HA failovers with oVirt?
by Matthew Trent 09 Jun '17

09 Jun '17

I'm using two TrueNAS HA SANs (FreeBSD-based ZFS) to provide storage via NFS to 7 oVirt boxes and about 25 VMs. For SAN system upgrades I've always scheduled a maintenance window, shut down all the oVirt stuff, upgraded the SANs, and spun everything back up. It's pretty disruptive, but I assumed that was the thing to do. However, in talking with the TrueNAS vendor they said the majority of their customers are using VMWare and they almost always do TrueNAS updates in production. They just upgrade one head of the TrueNAS HA pair then failover to the other head and upgrade it too. There's a 30-ish second pause in I/O while the disk arrays are taken over by the other HA head, but VMWare just tolerates it and continues without skipping a beat. They say this is standard procedure in the SAN world and virtualization systems should tolerate 30-60 seconds of I/O pause for HA failovers seamlessly. It sounds great to me, but I wanted to pick this lists' brain -- is anyone doing this with oVirt? Are you able to failover your HA SAN with 30-60 seconds of no I/O without oVirt freaking out? If not, are there any tunables relating to this? I see the default NFS mount options look fairly tolerant (proto=tcp,timeo=600,retrans=6), but are there VDSM or sanlock or some other oVirt timeouts that will kick in and start putting storage domains into error states, fencing hosts or something before that? I've never timed anything, but I want to say my past experience is that ovirt hosted engine started showing errors almost immediately when we've had SAN issues in the past. Thanks! -- Matthew Trent Network Engineer Lewis County IT Services

8 13

Host install common error
by FERNANDO FREDIANI 08 Jun '17

08 Jun '17

This is a multi-part message in MIME format. --------------B17F4A1A13CE833AC9902298 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello folks. One of the most (if not the more) annoying problems of oVirt is the known message "... installation failed. Command returned failure code 1 during SSH session ..." which happens quiet often in several situations. Scrubbing installation logs it seems that most stuff goes well, but then it stops in a message saying: "ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Setup validation': Cannot locate vdsm package, possible cause is incorrect channels" - followed by another message: "DEBUG otopi.context context.dumpEnvironment:770 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError('Cannot locate vdsm package, possible cause is incorrect channels',), <traceback object at 0x3131ef0>)]'" I am not sure why would it complain about the repositories as this is a Minimal CentOS 7 Install and the oVirt repository is added by oVirt-Engine itself so I assumed it added the most appropriate to its own version. I even tried to copy over the same repositories used on the Hosts that are installed and working fine but that message shows up again on the Install retries. Does anyone have any other hints where to look ? For reference my engine version running is: 4.1.1.6-1.el7.centos. Fernando --------------B17F4A1A13CE833AC9902298 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hello folks. One of the most (if not the more) annoying problems of oVirt is the known message "... installation failed. Command returned failure code 1 during SSH session ..." which happens quiet often in several situations. Scrubbing installation logs it seems that most stuff goes well, but then it stops in a message saying: "ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Setup validation': Cannot locate vdsm package, possible cause is incorrect channels" - followed by another message: "DEBUG otopi.context context.dumpEnvironment:770 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError('Cannot locate vdsm package, possible cause is incorrect channels',), <traceback object at 0x3131ef0>)]'" I am not sure why would it complain about the repositories as this is a Minimal CentOS 7 Install and the oVirt repository is added by oVirt-Engine itself so I assumed it added the most appropriate to its own version. I even tried to copy over the same repositories used on the Hosts that are installed and working fine but that message shows up again on the Install retries. Does anyone have any other hints where to look ? For reference my engine version running is: 4.1.1.6-1.el7.centos. Fernando </body> </html> --------------B17F4A1A13CE833AC9902298--

5 4

User Portal and Multi-Monitor Support
by Bryan Sockel 08 Jun '17

08 Jun '17

Is there a way to enable multi monitor support when launching a RDP Session through the user Portal? Bryan Sockel Systems Administrator Alt-N Technologies | Grapevine, TX Office 817.601.3222 x233 Sent using Alt-N's own MDaemon Messaging Server Get to know the Alt-N family by liking us on Facebook!

1 0