Ask Your Question

Adding a region broke block device mapping

asked 2015-10-28 15:38:10 -0600

Jeff C. gravatar image

I recently added a new region to our Openstack Juno install to cover a new site in our company. The setup uses the original Keystone authentication, but with a new controller, compute node(s) and block storage (cinder) node(s) in the new region. Horizon recognizes the new region, and I can create images and block volumes with no problem.

However, when I try to boot an instance using the newly created volume I get a "Block Device Mapping is Invalid: failed to get volume (HTTP 400)". This is the case in either the original or new region.

I also tried to launch an instance through Horizon in the new region (named 'bdradm') using 'Boot from Image (creates a new volume)'. This resulted in the following error: AmbiguousEndpoints: [{u'adminURL': u'', u'region': u'regionOne', u'internalURL': u'', 'serviceName': u'cind so I think the problem is with the endpoints in Keystone, as this attempt should have created the volume in region 'bdradm' instead of 'regionOne'.

I am using the same service, user and tenant for each type of service (nova, cinder, etc.), and then creating a new endpoint for each region. Is that the correct way to do it, or am I missing something?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2015-10-29 09:34:12 -0600

Jeff C. gravatar image

Add the following to /etc/nova/nova.conf for each node in each region. This will resolve the ambiguity.

os_region_name = *region*
edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2015-10-28 15:38:10 -0600

Seen: 67 times

Last updated: Oct 28 '15