settingsLogin | Registersettings

[openstack-dev] [infra][third-party] Some unknown updates broke nodepool connection to provider. Read for solution.

0 votes


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.

irc: asselin


OpenStack Development Mailing List (not for usage questions)
asked Aug 21, 2015 in openstack-dev by Asselin,_Ramy (4,700 points)   1 2 5