Red Hat Bugzilla – Bug 975786
VM migration fails when required network, configured with migration usages is turned down
Last modified: 2016-02-10 14:53:32 EST
Created attachment 762869 [details]
vdsm log of migration problem
Description of problem:
Configure required network with migration usages and turn down the NIC, the network resides on.
This action will initiate migration, which will fail as the migration network is down
Steps to Reproduce:
1.Install VM on Host A
2.Configure network x as required and migration on Host A and Host B
3.Turn down NIC the network x resides on
Migration starts and fails
Migration should succeed
One of the following should be considered as the solution for this case:
1) Rhevm network should be picked for the migration in case of the migration and required network failure (as in case of non-required migration network scenario)
2) Migration should fail, but then the same behaviour should be considered for the migration and non-required network
As far as I recall, we decided that if the migration network is missing, migration would fall back to the currently-used management network. Isn't it so, Alona?
Either way, the decision on which network to use and whether to perform migration, is at the hands of Engine, not Vdsm.
(In reply to Dan Kenigsberg from comment #1)
> As far as I recall, we decided that if the migration network is missing,
> migration would fall back to the currently-used management network. Isn't it
> so, Alona?
I haven't find any specific description of the expected behaviour on the feature page  for this case.
However, I don't see any alternative for migration other than using the management network.
Verified in IS15
Closing - RHEV 3.3 Released