On Fri, Nov 6, 2015 at 5:21 PM, Jason Keltz <j...@cse.yorku.ca> wrote:
> Hi. > > Last night, I upgraded my engine from 3.5 to 3.6. That went flawlessly. > Today, I'm trying to upgrade the vdsm on the hosts from 3.5 to 3.6 (along > with applying other RHEL7.1 updates) However, when I'm trying to put each > host into maintenance mode, and migrations start to occur, they all seem to > FAIL now! Even worse, when they fail, it leaves the hosts DOWN! If > there's a failure, I'd expect the host to simply abort the migration.... > Any help in debugging this would be VERY much appreciated! > > 2015-11-06 10:09:16,065 ERROR >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (org.ovirt.thread.pool-8-thread-4) [] Correlation ID: 658ba478, Job ID: >> 524e8c44-04e0-42d3-89f9-9f4e4d397583, Call Stack: null, Custom Event ID: >> -1, Message: Migration failed (VM: eportfolio, Source: virt1). >> 2015-11-06 10:10:17,112 ERROR >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (org.ovirt.thread.pool-8-thread-22) [2f0dee16] Correlation ID: 7da3ac1b, >> Job ID: 93c0b1f2-4c8e-48cf-9e63-c1ba91be425f, Call Stack: null, Custom >> Event ID: -1, Message: Migration failed (VM: ftp1, Source: virt1). >> 2015-11-06 10:15:08,273 ERROR >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (org.ovirt.thread.pool-8-thread-45) [] Correlation ID: 5394ef76, Job ID: >> 994065fc-a142-4821-934a-c2297d86ec12, Call Stack: null, Custom Event ID: >> -1, Message: Migration failed while Host is in 'preparing for maintenance' >> state. >> 2015-11-06 10:19:13,712 ERROR >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (org.ovirt.thread.pool-8-thread-36) [] Correlation ID: 6e422728, Job ID: >> 994065fc-a142-4821-934a-c2297d86ec12, Call Stack: null, Custom Event ID: >> -1, Message: Migration failed while Host is in 'preparing for maintenance' >> state. >> 2015-11-06 10:42:37,852 ERROR >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (org.ovirt.thread.pool-8-thread-12) [] Correlation ID: e7f6300, Job ID: >> 1ea16622-0fa0-4e92-89e5-9dc235c03ef8, Call Stack: null, Custom Event ID: >> -1, Message: Migration failed (VM: ipa, Source: virt1). >> 2015-11-06 10:43:59,732 ERROR >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (org.ovirt.thread.pool-8-thread-40) [] Correlation ID: 39cfdf9, Job ID: >> 72be29bc-a02b-4a90-b5ec-8b995c2fa692, Call Stack: null, Custom Event ID: >> -1, Message: Migration failed (VM: labtesteval, Source: virt1). >> 2015-11-06 10:52:11,893 ERROR >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (org.ovirt.thread.pool-8-thread-23) [] Correlation ID: 5c435149, Job ID: >> 1dcd1e14-baa6-44bc-a853-5d33107b759c, Call Stack: null, Custom Event ID: >> -1, Message: Migration failed (VM: www-vhost, Source: virt1). >> > > > The complete engine log, virt1, virt2, and virt3 vdsm logs are here: > > http://www.eecs.yorku.ca/~jas/ovirt-debug/11062015 > > Is vdsmd service still active on that hosts? > Jason. > > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users >
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users