Nova instance doesn't respond (ICMP/SSH/VNC) after live migration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Confirmed
|
High
|
Pavel Boldin | ||
5.0.x |
Won't Fix
|
High
|
Pavel Boldin | ||
5.1.x |
Won't Fix
|
High
|
Pavel Boldin | ||
6.0.x |
Won't Fix
|
High
|
Pavel Boldin | ||
6.1.x |
Won't Fix
|
High
|
Pavel Boldin | ||
7.0.x |
Won't Fix
|
High
|
Pavel Boldin | ||
8.0.x |
Confirmed
|
High
|
Pavel Boldin |
Bug Description
QEMU Ubuntu bug:
https:/
-------
api: '1.0'
astute_sha: f5fbd89d1e0e1f2
auth_required: true
build_id: 2014-09-17_21-40-34
build_number: '11'
feature_groups:
- mirantis
fuellib_sha: d9b16846e54f76c
fuelmain_sha: 8ef433e939425ea
nailgun_sha: eb8f2b358ea4bb7
ostf_sha: 64cb59c681658a7
production: docker
release: '5.1'
This issue was reproduced on CI during system test 'Check VM backed with ceph migration in simple mode' (both Ubuntu and CentOS):
And I was able to reproduce it manually. Here are the steps:
1. Deploy cluster (Ubuntu, simple, nova flatDHCP, Ceph for volumes & images; 1 controller and 2 compute+ceph nodes)
2. Create new instance, create new volume, attach volume to the instance, associate floating ip address with instance
3. Migrate (live) instance to the another compute node (e.g. nova live-migration --disk-over-commit Test01 node-3.
Expected result:
- instance successfully migrated and it is accessible
Actual:
- instance migration was completed and Nova reported that it's running, but it couldn't be reached over network (both public and private) or VNC (VM didn't respond on keys press, you can find screenshot in attachments)
After instance hard reboot it became accessible and fully operable. I didn't find errors in libvirt/qemu logs, but it seems that the issue is related to attached before migration volume, because live migration of instance without volumes works fine.
no longer affects: | fuel |
no longer affects: | fuel/5.0.x |
no longer affects: | fuel/5.1.x |
no longer affects: | fuel/6.0.x |
tags: | added: nova |
tags: | added: release-note |
tags: |
added: release-notes removed: release-note |
no longer affects: | mos/5.1.1-updates |
tags: | added: upgrades |
tags: |
added: release-notes-done removed: release-notes |
description: | updated |
Should this be included into Release Notes?
It there any workaround?