Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Whoa. I had a breakthrough. I tried manually logging in to the iscsi volume on the target compute node, and after that migration worked.

This implies that the migration code is either not logging in the iscsi volume on the target node, or is programmed to do it later, in this case after a check to see if it's there has already run and canceled the migration process.

Whoa. I had a breakthrough. I tried manually logging in to the iscsi volume on the target compute node, and after that migration worked.

This implies that the migration code is either not logging in the iscsi volume on the target node, or is programmed to do it later, in this case after a check to see if it's there has already run and canceled the migration process.

@darragh-oreilly The 4 minutes thing you experienced is probably because in block migration it copies the volume to the other compute node. In my case, when I did this, I watched as it copied the volume onto itself (thankfully it still worked afterward :) )