Bug #1687
Error return code on Postmigrate action may lead to "untracked" VMs
| Status: | Closed | Start date: | 12/07/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | - | |||
| Target version: | Release 4.0 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 3.8 |
Description
When a VM is migrated, and the postmigrate returns a non-zero code. The migration fails but the VM has been successfully migrated to the new host. This makes the auto-recover mechanism of Opennebula useless.
This issue will try to fix that by ignoring non-zero exit code but it should at least log the error.
Associated revisions
bug #1687: Do not fail after the livemigration is successfull (i.e. on clean, post (network) and post-migrate)
History
#1
Updated by Ruben S. Montero over 8 years ago
- Target version set to Release 4.0
#2
Updated by Ruben S. Montero about 8 years ago
- Assignee set to Ruben S. Montero
#3
Updated by Ruben S. Montero about 8 years ago
- Status changed from New to Closed
- Resolution set to fixed
We ignore failures of clean (vnet driver), post (vnet driver) and post-migrate. Logs are in VM log, but as the VM is running in the new host we cannot fail the migration.