In case the network is without a subnet, calling the validation
logic during the report phase leads to an error because the LSN
would have been already allocated during the migration phase.
Bypass the issue by calling the plugin directly, which is what
the validation logic does in the first place.
Closes-bug: #1313997
Change-Id: I14f77ae3b0cc147c4ea1c79e56bdd809de7c76a0
(cherry picked from commit 47e51e7521784f6a2edcfbf71a9aac0237e76e42)
Reviewed: https:/ /review. openstack. org/91378 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=f217479c610 52077df4b7aae33 3fb71448c834c0
Committed: https:/
Submitter: Jenkins
Branch: stable/icehouse
commit f217479c6105207 7df4b7aae333fb7 1448c834c0
Author: armando-migliaccio <email address hidden>
Date: Mon Apr 28 20:24:18 2014 -0700
NSX: fix migration for networks without a subnet
In case the network is without a subnet, calling the validation
logic during the report phase leads to an error because the LSN
would have been already allocated during the migration phase.
Bypass the issue by calling the plugin directly, which is what
the validation logic does in the first place.
Closes-bug: #1313997
Change-Id: I14f77ae3b0cc14 7c4ea1c79e56bdd 809de7c76a0 a2edcfbf71a9aac 0237e76e42)
(cherry picked from commit 47e51e7521784f6