VMware: booting multiple instances fails if image is not in cache
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Medium
|
Tracy Jones |
Bug Description
If you try to boot several VMs with a new image (which does not exist in the cache) all instances will fail until the 1st instance downloads the image to cache.
Since the nova boot commands are being handled async, the 1st one will start downloading the image to cache and the others will "think" that the image is there (since only the meta-data file is checked). This is a side affect of bug
https:/
The "workaround" is to always deploy an instance when a new image is added to glance. But the real fix should be 2 parts
1. make checking is the file is in cache more robust - i.e. validate the file is completely there (not just the meta data file)
2. if an image is in the middle of being downloaded to the cache, block the other instances at that point until the image download is complete.
Changed in nova: | |
assignee: | nobody → Tracy Jones (tjones-i) |
Changed in nova: | |
status: | New → In Progress |
Changed in nova: | |
importance: | Undecided → Medium |
Changed in nova: | |
status: | In Progress → Won't Fix |
Fix proposed to branch: master /review. openstack. org/46400
Review: https:/