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

If a customer has a VM snapshot our "List Azure resources" request will fail. #1313

Open
Makdaam opened this issue Feb 15, 2021 · 2 comments

Comments

@Makdaam
Copy link
Contributor

Makdaam commented Feb 15, 2021

API version 2020-06-01 for type snapshots in eastus doesn't exist.
Supported api versions are (older than 2020-06-01) + 2020-06-30, 2020-09-30, 2020-12-01
Breaks List Azure Resources Geneva Action in eastus.

Check ARO RP service logs for eastus RP 2021-02-15 14:30:24.618311 UTC for the full message of the exception.

@Makdaam Makdaam changed the title API version 2020-06-01 for type snapshots in eastus doesn't exist. If a customer has a VM snapshot our "List Azure resources" request will fail. Feb 15, 2021
@Makdaam
Copy link
Contributor Author

Makdaam commented Feb 15, 2021

The problem is limited to customers who generated VM snapshots in their cluster resource group.
Next steps:

  • check how the snapshots can be generated
  • add tests for other resources that can be generated this way (might require more API versions for other resource types)

@Makdaam
Copy link
Contributor Author

Makdaam commented Apr 15, 2021

During Azure List Resources another resource caused an exception of wrong API version for microsoft.operationalinsights/workspaces.

I think the proper fix to this issue is to handle the wrong API version exception by finding all available API versions for an unknown resource and picking one.

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 a pull request may close this issue.

1 participant