Comment 8 for bug 1461055
Revision history for this message
| Oleksandr Savatieiev (osavatieiev) wrote | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hit this issue on Queens. The behavior is the same as above.
Tried already with no success:
- Reset state
- Forced
- Investigating logs shows that nova keeps "checking" those for something
- Once nova-compute service restarted it starts the instance update task and deletes those fake instances.
My personal best guess is that something wrong with the communication channel while Nova compute has its hands full running instances (degraded performance)