commit 68ec6840dd75dea85b6a55310c487284d7bd579e
Author: Daniel P. Berrange <email address hidden>
Date: Fri Sep 19 13:41:54 2014 +0100
libvirt: avoid changing UUID when redefining nwfilters
libvirt >= 1.2.7 enforces that when you re-define a network
filter you can't change the UUID. ie name + uuid must match.
Since Nova was not including any UUID in the XML it sent, it
would always get a random UUID generated, which would cause
failures when re-defining an existing filter. The result
was that Nova would fail to start up and fail to migrate
if there was an existing guest running. The fix is to query
libvirt to see if the nwfilter already exists, and extract
the UUID from its XML and use that when re-defining it.
(cherry picked from commit 2418a9dce86280fbf269f68f7d7c9b739f662ef1)
Reviewed: https:/ /review. openstack. org/167144 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=68ec6840dd7 5dea85b6a55310c 487284d7bd579e
Committed: https:/
Submitter: Jenkins
Branch: stable/icehouse
commit 68ec6840dd75dea 85b6a55310c4872 84d7bd579e
Author: Daniel P. Berrange <email address hidden>
Date: Fri Sep 19 13:41:54 2014 +0100
libvirt: avoid changing UUID when redefining nwfilters
libvirt >= 1.2.7 enforces that when you re-define a network
filter you can't change the UUID. ie name + uuid must match.
Since Nova was not including any UUID in the XML it sent, it
would always get a random UUID generated, which would cause
failures when re-defining an existing filter. The result
was that Nova would fail to start up and fail to migrate
if there was an existing guest running. The fix is to query
libvirt to see if the nwfilter already exists, and extract
the UUID from its XML and use that when re-defining it.
(cherry picked from commit 2418a9dce86280f bf269f68f7d7c9b 739f662ef1)
Closes-bug: #1360119 23ed79ed8e0b5ac 0d4418851a4
Change-Id: I9d4b2c6c8f0c9a