fix(xo-server/PIF): call PIF.forget to delete PIF (#7221)

Fixes #7193

Calling `pif.destroy` generates PIF_IS_PHYSICAL error when the PIF has been
physically removed
This commit is contained in:
MlssFrncJrg 2023-12-18 14:41:58 +01:00 committed by GitHub
parent 32afd5c463
commit ceddddd7f2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 1 deletions

View File

@ -22,6 +22,7 @@
- [REST API] Returns a proper 404 _Not Found_ error when a job does not exist instead of _Internal Server Error_
- [Host/Smart reboot] Automatically retries up to a minute when `HOST_STILL_BOOTING` [#7194](https://github.com/vatesfr/xen-orchestra/issues/7194) (PR [#7231](https://github.com/vatesfr/xen-orchestra/pull/7231))
- [Plugin/transport-slack] Compatibility with other services like Mattermost or Discord [#7130](https://github.com/vatesfr/xen-orchestra/issues/7130) (PR [#7220](https://github.com/vatesfr/xen-orchestra/pull/7220))
- [Host/Network] Fix error "PIF_IS_PHYSICAL" when trying to remove a PIF that had already been physically disconnected [#7193](https://github.com/vatesfr/xen-orchestra/issues/7193) (PR [#7221](https://github.com/vatesfr/xen-orchestra/pull/7221))
### Packages to release

View File

@ -28,7 +28,7 @@ async function delete_({ pif }) {
return
}
await xapi.callAsync('PIF.destroy', pif._xapiRef)
await xapi.callAsync('PIF.forget', pif._xapiRef)
}
export { delete_ as delete }