[PR #4508/8076f16a backport][stable-4] Correctly handle exception when no VM name returned by proxmox #4529
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #4508 as merged into main (8076f16).
SUMMARY
Handle a case when proxmox didn't return the VM name, which is generally wrong behavior on proxmox side, but can happen and we shouldn't fail.
ISSUE TYPE
COMPONENT NAME
proxmox_kvm
ADDITIONAL INFORMATION
I was running a task:
and randomly (a frequency is 1/20, but maybe it depends on the API calls load on the backend proxmox) I get the failure like:
The python error nicely formatted: