Skip to content
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

Add multiple retries and timeout for getting vm resources in proxmox … #51013

Merged
merged 1 commit into from
Dec 31, 2018

Conversation

BrianSidebotham
Copy link
Contributor

…cloud. Fixes #49485

What does this PR do?

Introduces more resilient querying of VMs through the proxmox driver when trying to get the VM resources from proxmox.

What issues does this PR fix or reference?

Fixes issue #49485

Previous Behavior

After creating a VM via the proxmox API, the machine is un-named. If salt-cloud's proxmox driver queries fast enough after the creation of the VM, the resource will be returned without a name key. This causes the proxmox driver to fail (Raise an unhandled KeyError exception).

New Behavior

The API request is attempted multiple times for a certain period of time and if the proxmox API query continually fails we raise a saltcloud timeout exception instead.

Tests written?

No

Commits signed with GPG?

No

Please review Salt's Contributing Guide for best practices.

See GitHub's page on GPG signing for more information about signing commits with GPG.

@BrianSidebotham
Copy link
Contributor Author

I can't see any of the drill-down info for the tests that have failed. I'm not sure what in this merge is causing an issue.

@dwoz dwoz merged commit 99966fc into saltstack:develop Dec 31, 2018
@waynew waynew removed the master-port label Dec 2, 2019
@terminalmage
Copy link
Contributor

Ported to master in #56705

dwoz added a commit that referenced this pull request Apr 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants