-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
feat(vm): fix adding/removing hostpci devices forcing vm recreation #504
feat(vm): fix adding/removing hostpci devices forcing vm recreation #504
Conversation
@bpg I'm trying to work on this. Changing the Removing hostpci devices on the other hand does not work as expected:
As I'm not famliar with the code base would you mind giving me some pointers where to start analyzing? |
Thanks for taking care of this @michaelze! I'll take a look on the weekend and get back to you. Will try to merge all the opened PRs and have a solid release 🙂 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, I know where is the problem with delete -- PVE API requires deleted devices to be explicitly listed in delete
attribute of the update body. This piece was missing for hostpci
as you know... they were not meant to be updated without the VM destroy 😅
So I've took a liberty to add it to your PR.
I've also fixed a separate bug with device IDs that was introduced in #500.
So I'm just going to merge this PR.
Thanks for contributing @michaelze!
@all-contributors please add @michaelze for bug |
I've put up a pull request to add @michaelze! 🎉 |
@bpg Now that is some good news to have in your inbox on a monday morning 😄! |
Contributor's Note
Please mark the following items with an [x] if they apply to your PR.
Leave the [ ] if they are not applicable, or if you have not completed the item.
/docs
for any user-facing features or additions./examples
for any new or updated resources / data sources.make examples
to verify that the change works as expected.Community Note
Closes #503