-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
"VirtualMachine matching query does not exist." when trying to delete Virtual Machines #2323
Comments
Just tried this with 2000 virtual machines and wasn't able to reproduce the error. All 2000 VMs were deleted. Can you try it with |
@jeremystretch: Will do. I just tried to delete a single VM, and got the same error. Stack trace:
|
Ok, the issue seems to stem from logging the deletion of the VM interfaces rather than the VMs themselves. |
For some reason, the interfaces are being deleted after the VM gets deleted. As far as I can tell, only interfaces are affected: Other related objects (secrets, etc.) get deleted before the VM as they should. The exception is being raised when calling |
Well then. Hrmm... Is this something I could have caused? The system's provenance is 2.3.2 upgraded successively to 2.4.1. |
@pm17788 No, it's an anomaly in the way Django chooses to order the deletion of related objects. I have a fix coming in v2.4.2. |
Environment
Steps to Reproduce
Select all 1686 virtual machines matching query
checkboxDelete All
buttonDelete these 1686 virtual machines
buttonExpected Behavior
1686 selected Virtual Machines razed into oblivion
Observed Behavior
Server Error
page with the following text:The text was updated successfully, but these errors were encountered: