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

Inventory failing when flexible and uniform scalesets in the same RG #1431

Open
Justwmz opened this issue Feb 5, 2024 · 1 comment
Open
Labels
bug Something isn't working has_pr PR fixes have been made medium_priority Medium priority

Comments

@Justwmz
Copy link

Justwmz commented Feb 5, 2024

SUMMARY

Inventory fails when flexible and uniform scale sets in the same RG.
I can see instances of the flexible scale set if the params "include_vmss_resource_groups" are not assigned.
I think it is because instances in the flexible scale set are created as standalone VMs, so Ansible is able to represent them in the inventory output.
But when I add back include_vmss_resource_groups, inventory is falling.
It seems to me like ansible is not able to parse a list of the instances from the flexible scale set since they have a different machine type.

ISSUE TYPE
  • Bug Report
COMPONENT NAME

azure.azcollection

ANSIBLE VERSION

2.16.0

COLLECTION VERSION

2.1.1

STEPS TO REPRODUCE

Create two types of scale sets in the same RG.
In the inventory assign the params below:
include_vm_resource_groups:
- name of the RG
include_vmss_resource_groups:
- name of the RG

EXPECTED RESULTS

Inventory output should present instances from both types of scale sets.

@Fred-sun

This comment was marked as resolved.

@Fred-sun Fred-sun added has_pr PR fixes have been made bug Something isn't working and removed work in In trying to solve, or in working with contributors labels Feb 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working has_pr PR fixes have been made medium_priority Medium priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants