I still think this is a valid bug. The problem disappeared after nova-network restart and so far it did not come back. What we would like to find out is why did this start happening. There is no proof of this but it may be ralated to long nova-network uptime. Changing the values as you suggested could only delay the problem, there is no guarantee that the root cause is caused by low thresholds. If it was the thresholds why would the problem disappear after restart?
Also if you suggest that default values could cause problems should they not be updated? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1144108 Title: Unable to create instances due to QueuePool limit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1144108/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
