-
Notifications
You must be signed in to change notification settings - Fork 334
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
Error retrieving resource group xxxxxxxx - API version 2022-09-01 does not have operation group 'resource_groups' #1762
Comments
@vijayreddiar Welcome you submit your problems, because we upgraded the half cup v3.0.0 and also upgraded azure-mgmt-resource to version v23.1.0(refer to PR #1712), can you check the version of azure-mgmt-resource? Thank you! |
@Fred-sun We are using AWX running on k3s and the project containing
For the specific version of We follow the installation procedure from this repo which results into 4 different pods -
So, I doubt whether it uses the above package and runner depends something else or the issue might be existing even with |
@vijayreddiar I confirmed v23.1.0 this time(Relate link Line 28 in 051dc18
|
@Fred-sun The output shared in my previous comment also confirms |
@vijayreddiar I'm very sorry to reply you so late. But I checked that the 'resource_groups' of API 'v2022-09-01 exists, is it because your installation environment and execution environment are inconsistent? Could you confirm that? Thank you very much! |
SUMMARY
Modules under azure.azcollection
v3.0.0
fails whenresource_group
is required. The same is working without any issue when downgraded tov2.7.0
ISSUE TYPE
COMPONENT NAME
azure_rm_virtualmachine
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
RHEL 8.8 / AWX v24.6.1 (Installed and configured using awx-on-k3s)
STEPS TO REPRODUCE
Install latest version (v3.0.0) of azure.azcollection and attempt to start or stop an Azure VM using the module azure_rm_virtualmachine
EXPECTED RESULTS
Azure VM should be stopped and the same is working as expected with azure.azcollection v2.7.0
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: