-
Notifications
You must be signed in to change notification settings - Fork 93
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
hydra clean-resources
for Azure for a user in dry-run mode doesn't show existing resources
#8582
Comments
see
In that case it's not showing individual resources. |
It differs from how it performs for other backends, e.g.:
The same for aws. So when a person would expect the same behavior for azure as well, it can confuse (it was with me, I understood that azure backend has my resources alive only when listed them directly, not when executed |
hydra clean-resources
for Azure in dry-run mode doesn't show existing resourceshydra clean-resources
for Azure for a user in dry-run mode doesn't show existing resources
dry-run for clean resources shows the action taken for cleaning resources. In terms of azure it would delete everything (meaning whole resource group) and dry-run shows exactly that - I don't see an issue with discrepancy between list-resources and clean-resources dry-run. |
Users are not completely aware for those differences between the backends, but output of dry-run is mostly cosmetic. On the other hand for logging purpose in CI runs, having the resources listed might be helpful, and we iterate the VMs for reporting to Argus anyhow |
but do we iterate using 'clean-resources'? I doubt it. |
So how does Argus get the report in Azure case ? |
|
Didn't suggest parsing the output I was asking how Argus gets the information that resources are clean, when it was as part of the clean resources stage ? If the answer is that it doesn't, then the data we have on Argus about nodes isn't very accurate, isn't it ? |
Yes, there's still some problem with marking Azure nodes upon clean-resources stage. I'll take a look at it. |
Even though resources exist on Azure backend, the
hydra clean-resources --dry-run
command for a user doesn't list them.For other backends (aws, gce, etc.) the resources are listed when
hydra clean-resources --dry-run
command is executed for the backend for a user.Ex.:
The issue is rather cosmetic, but can sometimes confuse a user, when the list of resources available for cleanup in Azure is requested and it doesn't return any items.
The text was updated successfully, but these errors were encountered: