Hi everyone, on our test we have a workaround. After volume retype, cold migrating the instance updates the pool name on guest xml and creates a new volume attachment which contains the new pool name on the attachment properties.
Hi everyone, on our test we have a workaround. After volume retype, cold migrating the instance updates the pool name on guest xml and creates a new volume attachment which contains the new pool name on the attachment properties.