Hmm, might be that when nova attaches the volume it's assuming /dev/vdb is available and that's what it tells cinder it's going to attach to:
https://github.com/openstack/nova/blob/a023c32c70b5ddbae122636c26ed32e5dcba66b2/nova/virt/block_device.py#L304
But the block_device_info code isn't taking into account the config drive? Probably need ndipanov to look at this.
Hmm, might be that when nova attaches the volume it's assuming /dev/vdb is available and that's what it tells cinder it's going to attach to:
https:/ /github. com/openstack/ nova/blob/ a023c32c70b5ddb ae122636c26ed32 e5dcba66b2/ nova/virt/ block_device. py#L304
But the block_device_info code isn't taking into account the config drive? Probably need ndipanov to look at this.