[SRU] Parallel VM creation fails when nova-computes share the disks and each nova-compute node has no cached images.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Mandar Vaze | ||
Essex |
Fix Released
|
Undecided
|
Unassigned | ||
nova (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Chuck Short |
Bug Description
Scenario:
1. There are two nova-compute Hosts : HostA and HostB
2. NFS server : HostC exports "/shared_
3. Both HostA and HostB mount HostC:/
4. Both HostA and HostB have "instances_
5. HostC:/
6. Two VMs are launched from the same image at the same time (Parallel VM creation)
7. Since there are no cached images in <instances_
This seems like problem related to file locking.
Since these are two different compute hosts, @utils.synchronized is not useful.
Expected Response:
Parallel VM Creation as explained above should not fail.
Actual Response:
using same disk area from multiple nova-compute crashes instance images.
Reported on :
Branch: master
git commit : d9019f7aa6e1817
Related branches
- Chuck Short: Pending requested
-
Diff: 56 lines (+14/-4)3 files modifieddebian/changelog (+8/-0)
debian/control (+6/-3)
debian/nova-console.install (+0/-1)
tags: | added: essex-backport |
Changed in nova: | |
milestone: | none → folsom-1 |
importance: | Undecided → Medium |
Changed in nova: | |
status: | Fix Committed → Fix Released |
affects: | glance (Ubuntu) → nova (Ubuntu) |
Changed in nova (Ubuntu): | |
status: | New → In Progress |
Changed in nova (Ubuntu Precise): | |
status: | New → In Progress |
Changed in nova (Ubuntu Precise): | |
assignee: | nobody → Chuck Short (zulcss) |
milestone: | none → ubuntu-12.04.1 |
tags: |
added: verification-done removed: verification-needed |
Changed in nova (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in nova: | |
milestone: | folsom-1 → 2012.2 |
Proposed fix :
instead of using _base folder to store cached image, use "_base_ <compute_ hostname> " so that in above scenario, images will be cached in _base_HostA and _base_HostB respectively - preventing the file locking issue.