XendAPI: After VBD_destroy and VIF_destroy the managed config must be saved

...otherwise already deleted devices appear again in configuration
after a xend restart.

Signed-off-by: Lutz Dube <Lutz.Dube@ts.fujitsu.com>
This commit is contained in:
Keir Fraser committed 2009-12-29 15:04:17 +00:00
1 parent bd9d6a42bc
commit f0a326072f
1 file changed
+3
+3
View File
@@ -2053,6 +2053,7 @@ class XendAPI(object):
XendTask.log_progress(0, 100, vm.destroy_vbd, vbd_ref)
xendom.managed_config_save(vm)
return xen_api_success_void()
def _VBD_get(self, vbd_ref, prop):
@@ -2220,6 +2221,8 @@ class XendAPI(object):
return xen_api_error(['HANDLE_INVALID', 'VIF', vif_ref])
vm.destroy_vif(vif_ref)
xendom.managed_config_save(vm)
return xen_api_success_void()
def _VIF_get(self, ref, prop):
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.