Bug #1400

After a migration fails the history records reach an inconsistent state

Added by Ruben S. Montero almost 9 years ago. Updated over 8 years ago.

Status:ClosedStart date:08/02/2012
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:

0%

Category:Core & System
Target version:Release 3.8
Resolution:fixed Pull request:
Affected Versions:OpenNebula 3.6

Description

This seems to be because of a missing update of the DB. So if oned is restarted it gets the wrong REASON field. As a result the VM can not be migrated.

Associated revisions

Revision cabf3b41
Added by Ruben S. Montero almost 9 years ago

bug #1400: Update History record when a migration fails.

Revision 7553a431
Added by Ruben S. Montero over 8 years ago

bug #1400: Update History record when a migration fails.
(cherry picked from commit cabf3b417e62d87c9cfe465301e5cc6e6e5865b0)

History

#1 Updated by Ruben S. Montero over 8 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF