-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't Remove PIF #7193
Comments
Thanks a lot for the report 👍 |
@olivierlambert So XO should automatically call |
Ask @Fohdeesha for confirmation |
I think this would be acceptable, yes. If not just calling PIF forget always instead of destroy. They both fully remove the PIF from XAPI as far as I know, Citrix's own documentation seems to call pif forget and not destroy when removing NICs: https://support.citrix.com/article/CTX127161/how-to-replace-a-network-interface-card-in-a-xenserver-host - however maybe we should ask @stormi for confirmation on the difference. |
I have no idea but if needed we can ask someone in the XCP-ng Team to have a look at the code. |
I think that's the right approach. But yeah, let's do it in XO, and make some functional test on the XCP-ng team when the branch is ready to confirm it works as expected 👍 |
@julien-f I let you assign the right XO dev on this |
Fixes #7193 Calling `pif.destroy` generates PIF_IS_PHYSICAL error when the PIF has been physically removed
Describe the bug
When trying to remove a PIF in Xen Orchestra CE 5fe53 of a removed physical adapter, an error message is received "PIF_IS_PHYSICAL()".
To Reproduce
Expected behavior
For physical PIFs,
pif-forget
should be used on the backend to remove physical NICs.Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please provide the following information):
Additional context
Conversation at Forums and GitHub Docs Contribution
The text was updated successfully, but these errors were encountered: