nova-compute charm should configure an unique host_uuid on libvirtd.conf
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nova-compute (Juju Charms Collection) |
Fix Released
|
Medium
|
Xiang Hui | ||
Bug Description
1. Description of the problem:
when live migration is performed on where nova-compute charm deployed, the following error occurred.
2014-04-10 14:29:42.262 7662 ERROR nova.virt.
[instance: 8115a225-
failure: internal error: Attempt to migrate guest to the same host
03000200-
It appears the value of host_uuid which libvirt takes on every compute node are all same.
libvirt takes the value of host uuid running "dmidecode -s system-uuid".
It however depends on value provided by hardware vendor.
It doesn't provide always a valid unique id.
https:/
To prevent this issue,
I think nove-compute charm should configure this value with "uuidgen" explicitly.
2. Ubuntu release, software version, Release Number and Architecture of the selected components.
Ubuntu : 12.04 LTS
Charm : cs:precise/
3. How reproducible is the problem?
Always, if "dmidecode -s system-uuid" doesn't return a valid unique id.
4. Steps to Reproduce:
a. Actual Results:
In some cases, host_uuid which libvirtd recognizes are not unique.
b. Expected Results:
host_uuid has to have a unique value across nova-computing nodes.
5. Known Workaround:
Configured host_uuid manually and live migration works fine.
Related branches
- Edward Hope-Morley: Approve
-
Diff: 77 lines (+26/-9)3 files modifiedhooks/nova_compute_context.py (+3/-0)
templates/libvirtd.conf (+1/-0)
unit_tests/test_nova_compute_contexts.py (+22/-9)
| Changed in nova-compute (Juju Charms Collection): | |
| status: | In Progress → Fix Committed |
| Changed in nova-compute (Juju Charms Collection): | |
| status: | Fix Committed → Fix Released |
