-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Sorting is not always working correct #83208
Comments
Files identified in the description: None If these files are incorrect, please update the |
@dcz010 |
I was not able to reproduce the issue. inventory:
playbook: - hosts: localhosts
gather_facts: false
order: sorted
serial: 1
tasks:
- debug: output:
Omitting For us to be able to move this issue forward we need a minimal and complete reproducer. |
Hi @mkrizek |
Here starts it with the ngx-01 and not with normally ha-01:
And normally like:
|
I just ran the playbook I provided in a shell for loop 100 times, each time the output was as expected.
This still stands as you have not provided complete reproducer. The output itself is not sufficient for us to do anything about this issue unfortunately. |
Mhm well ok.
|
Both of those versions are unsupported and several years old, please see #83208 (comment). |
It seems like the problem is something with the factsCache:
Here you can also see the order with the creation time of the folder. Is there an option to ignore that cache? |
But now i could reproduce it and i let the playbook with debug info run:
Is there anything not normal? |
But i will then update the old machine with an new ansible version and try again. |
Summary
Normally the sorting of ansible is fine and works correct, but sometimes it doesn't and then it shuffels the hostnames and so not our haproxys aren't the first ones to get an downtime and alarms are coming.
Is this sorting a bug from ansible or in another plugin/library?
Our site.yml looks:
Issue Type
Bug Report
Component Name
order
Ansible Version
Configuration
OS / Environment
Debian 11
Steps to Reproduce
Expected Results
I expect an always normally working sorting of the hosts in alphabetical order like configured.
Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: