-
Notifications
You must be signed in to change notification settings - Fork 313
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
azure.azcollection.azure_rm_virtualmachinescalesetinstance_info and related modules incompatible with Flexible VM Scale Sets #1526
Comments
#1529 has fixed this bug! |
When will this get released? |
Also @Fred-sun it seems this change was only completed on the azure_rm_virtualmachinescalesetinstance_info module, do further changes need to be made on the other modules such azure_rm_virtualmachinescaleset and azure_rm_virtualmachinescalesetinstance ? Thanks |
@nscriptdotgo It should be released early next month. azure_rm_virtualmachinescaleset doesn't need to change, only need to synchronize changes azure_rm_virtualmachinescaleinstance. py, has been submitted. Thank you! |
SUMMARY
When trying to get ScaleSet Instance information for a Flexible Scaleset using the azure.azcollection.azure_rm_virtualmachinescalesetinstance_info module, I get this error:
Virtual Machine Scale Set VM instanceId must be a number.
However, per the Azure documentation here: https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-instance-ids#scale-set-instance-id-for-flexible-orchestration-mode
The scaleset instanceId of a Flexible scaleset is just name of the virtual machine. The module should be able to handle both a Uniform and Flexible scalesets.
ISSUE TYPE
COMPONENT NAME
azure_rm_virtualmachinescalesetinstance_info and possibly the others.
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
Target OS is Windows 11 in a flexible scaleset
STEPS TO REPRODUCE
az login and run a playbook similar to the following below:
EXPECTED RESULTS
I expected to recieve back some information about the VMSS
ACTUAL RESULTS
The module errors out because of the returned instanceIds not being a number.
The text was updated successfully, but these errors were encountered: