Comment 1 for bug 1681998

Yeah we did attempt to fix this with [2] but couldn't find a reasonable way to handle >1 bdm with the same instance_uuid and volume_id.

I don't think connection_info being NULL is the correct way to avoid this as all newly created BDMs would meet this criteria, making it impossible for us to find the BDM later when calling intialize_connection etc.

Should we mark this as a duplicate of bug#1427060 and continue there?