Instance sometimes do not fully terminate, causes crash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Anthony Young |
Bug Description
I can reproduce a situation where instances do not fully terminate. In this situation, instance backing files are deleted, but the domain still exists in libvirt. Then, due to this bug: https:/
Steps to reproduce:
> (run devstack)
> cd exercises
> # the following script launches 2 instances in quick succession, and then terminates after 10 seconds
> curl https:/
> chmod 755 test.sh
And then:
> ./test.sh
Repeat this command 4-8 times. Then:
> sudo virsh list
Expected:
No domains
Actual:
$ sudo virsh list
Id Name State
-------
19 instance-00000002 running
29 instance-0000000c running
Then, nova-compute starts spitting this error:
2012-03-15 23:10:09 ERROR nova.manager [-] Error during ComputeManager.
And upon next restart, the process crashes
summary: |
- Instance sometimes do not fully terminated, causes crash + Instance sometimes do not fully terminate, causes crash |
description: | updated |
Changed in nova: | |
milestone: | none → essex-rc1 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in nova: | |
assignee: | nobody → Anthony Young (sleepsonthefloor) |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-rc1 → 2012.1 |
I'm not sure if https:/ /bugs.launchpad .net/nova/ +bug/957110 is exactly the same issue,
but the symptom is the same.
The patch provided there only mitigates the symptom,
allowing the compute service to start (and logging an error about the missing disk file)