-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Remove virt.pool_delete fast parameter #54475
Conversation
I took a look at this PR and the area of code it touches, and I am certainly no expect but I see that you @cbosdo have quite a lot of code in this file so I will approve it. However, I will ask that you rebase and target |
1650eeb
to
35bc98e
Compare
35bc98e
to
092ee95
Compare
@xeacott rebased on master and added a unit tests for that function... even though it doesn't test that parameter removal |
Thank you! |
a0b9d54
to
e981ac1
Compare
There are two reasons to remove this parameter without deprecating it: * the meaning has been mistakenly inversed * fast=True will raise an exception for every libvirt storage backend since that flag has never been implemented in any of those. Fixes issue saltstack#54474
e981ac1
to
f530047
Compare
The windows tests are passing but the build failed due to some left open file handles. |
What does this PR do?
There are two reasons to remove this parameter without deprecating it:
since that flag has never been implemented in any of those.
What issues does this PR fix or reference?
Fixes issue #54474
Previous Behavior
salt 'kvmsrv' virt.pool_delete mypool
fails with a libvirt exceptionNew Behavior
salt 'kvmsrv' virt.pool_delete mypool
actually deletes the pool is that function is supported by the libvirt storage backend.Tests written?
No, trivial function even when the fast parameter existed, even simpler now.
Commits signed with GPG?
Yes