Comment 4 for bug 1321798

This is due to the fact that the logic of attaching a volume, and detaching a volume for the copy_image_to_volume process actually exists in the base driver.py's _attach_volume() method. The volume manager itself handles attaching volumes in initialize_connection, which is where the FibreChannel Zone Manager code is being called.

We might need to refactor some code here, because the driver.py shouldn't have it's own copy of the ZoneManager just to zone up FC attach/detaches for this process.