Block device type for block_mapping_device is not configurable

Bug #1394625 reported by Denis M.
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Invalid
High
Unassigned

Bug Description

Block device type for block_mapping_device is not configurable.

In code we're doing something like this:

 volume_info = {
'block_device': {'vdb': "%s:%s:%s:%s" % (volume.id '', volume.size, 1)},
'device_path': '/dev/vdb',
'mount_point': mount_point,
'volumes': [{'id': v_ref.id, 'size': v_ref.size}]
}

# <id>:[<type>]:[<size(GB)>]:[<delete_on_terminate>]
block_device_mapping = {'vdb': "%s:%s:%s:%s" % (volume.id, '', volume.size, 1)}

nova_client.servers.create(..., block_mapping_device=block_device_mapping)

As it can be seen, Trove hardcodes block device type to 'vdb' - it's only valid for "virtio", for example for iSCSI - sdb

And nova raises error - InvalidBDM: Block Device Mapping is Invalid

Denis M. (dmakogon)
description: updated
description: updated
Revision history for this message
Auston McReynolds (amcrn) wrote :
Revision history for this message
Denis M. (dmakogon) wrote :

 Sure, we need to find out proper solution and see if nova can deal with it for us.

Denis M. (dmakogon)
Changed in trove:
milestone: kilo-1 → none
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.