Thanks, Unmesh. My nova.conf on my compute node had some conflicting
settings. E.g. I am using quantum, but I still had network_manager =
nova.network.manager.FlatDHCPManager.
That error is gone. But naturally I have new ones now. I'll start a new
thread for that :)
On Fri, Feb 8, 2013 at 12
Greg,
IMO, this qualifies as a bug.
To debug what's causing this scenario is your case, I would suggest
checking the database connection setting in nova.conf on your Compute &
Controller host. AFAIK, it either means Compute's status is not being
updated (Compute service down) or its being updated
So I'm getting this when I try to boot a Cirros image in scheduler.log. I
have a controller node, network node, and one compute node setup with
Folsom on RHEL 6. Any ideas? Thanks!
2013-02-07 19:21:45 WARNING nova.scheduler.manager
[req-358f5c96-e236-4167-b6a9-ccc02c853d41 65fdf1a86cfa4e50aafb6
3 matches
Mail list logo