Comment 8 for bug 1112483

Here is the updated patch..

WARNING: This patch significantly changes how Essex is handling volume connect/disconnect.

The cleanest option to address the problem of reusing LUN id was to remove the information about the old LUN id from the database. After this patch, code will wipe-out "connection_info" column from "block_device_mapping" table, when volume is disconnected. I found only two places in Essex where it needs to be done. There are couple more in 'master' branch. So, this patch should only be applied Essex and would need significant update for later releases.

If there is no info in DB on what was the LUN id when this volume was connected, then there is no chance that any future call to 'disconnect_volume' will cause harm to volume using the same LUN id now..

You may also look at related mail-thread with "Libvirt iSCSI client: duplicit connection_info data" subject..