Public bug reported: When I'm trying to boot instances on a specific host (sleepy) by issuing:
nova boot --image mybucket/image.manifest.xml --flavor m1.tiny --key_name mykey --hint force_hosts=sleepy test-vm my VMs always seem to start on a random host instead on the one I targeted. I'm using Essex and the filter scheduler (my nova.conf contains `compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler`). My user is admin (I sourced /var/lib/nova/novarc), I also have --allow_admin_api=true in my nova.conf file. The only mention of filter in my /var/log/nova-scheduler.log is > u'filter_properties': {u'scheduler_hints': {u'force_hosts': u'sleepy'}}. This file also says u'_context_is_admin': True and u'_context_roles': [u'admin'] Here is the full request grabbed from the nova-scheduler.log file: http://paste.ubuntu.com/1260083/ The matter was also discussed in this AskUbuntu question: http://askubuntu.com/questions/169625/why-cant-i-get-nova-openstack-to- use-a-specific-host I'm running Ubuntu server 12.04 and nova-scheduler version 2012.1-0ubuntu2. ** Affects: nova (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1061665 Title: Filter scheduler not respecting the force_hosts hint To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1061665/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs