All, Recently, some external dependency broke nodepool's ability to launch VMs on an openstack provider. If you haven't run into this yet, it's probably because you haven't restarted nodepool. When you do, you might get an error similar to [1]
I couldn't find the issue, but regardless, there's a fix to nodepool that's been merged [2]. However, you do need to update your nodepool.yaml configurations to use 'project-name' instead of 'project-id'. Here's an example [3] I don't know the solution if you're using cloud.yaml, but it should be similar. Ramy irc: asselin [1] http://logs.openstack.org/54/211754/4/check/gate-dsvm-nodepool-nv/958471b/logs/screen-nodepool.txt.gz#_2015-08-18_22_59_57_227 [2] https://review.openstack.org/#/c/214399/2 [3] https://github.com/rasselin/os-ext-testing-data/commit/00dcce696c7fb8d3b5e55e1984ebb2bff9edfcb2
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
