ansible

[Ansible] Summary Since your last visit 10 2 35 New Topics Unread Notifications New Users Popular Topics Project Discussions October 30 Proposal: trimming down the Ansible community package and collection removal roadmap Andersson007 Following the adoption of the new collection inclusion criteria, I propose discussing a roadmap to remove collections that no longer meet the criteria from the Ansible community package. 8 19 Read More Get Help October 27 Role deduplication fails with `-‌-skip-tags always` mirabilos For Ansible 2.19, reduced to the following: Playbook: Roles: When called as env ANSIBLE_GATHERING=explicit ansible-playbook -t has-roles --skip-tags always $playbookname, the mysql_mariadb_common role is ran twice (once before each of the depending roles). 3 4 Read More Ecosystem Releases October 27 Release announcement: Ansible community package 15.0.0a4 (Pre-Release) Maxwell G (He/They) gotmax23 Hello everyone, We’re happy to announce the release of the Ansible 15.0.0a4 package pre-release! Ansible 15.0.0a4 depends on ansible-core 2.22.0rc2 and includes a curated set of Ansible collections that provide a vast number of modules, plugins, and roles. This is a pre-release of Ansible 15. 0 0 Read More Get Help October 30 Help wanted with AWX / AKS problem ildjarn I hope someone can help me. I upgraded the node pool for our AKS cluster from 2 Standard_D4s_v3 servers to 2 Standard D4as_v7 servers. The nodes are almost picking their nose because they have very little to do, but since the upgrade I get the following error a few times now: Task was marked as running but was not present in the job queue, so it has been marked as failed. I can’t imagine that the change from D4s to D4as has that much impact on the performance of AWX, and CPU/Memory of the nodes never reach very high levels (highest memory usage of the node I’ve seen was around 60%). 0 0 Read More Ecosystem Releases October 27 New Release: ansible-core v2.22.0rc2 Ansible Announcements ansible-announce View this release on: - GitHub - PyPI See the full changelog for the changes included in this release. - Built Distribution: ansible_core-2.22.0rc2-py3-none-any.whl - ‌2488608 bytes - 7914e7bdcd32ee928ae57fb815d6982f225e561d7fc7b81f97eb2cc247fd4077 (SHA256) - Source Distribution: ansible_core-2.22.0rc2.tar.gz - ‌3481732 bytes - 16799131f8b2e2176b2e07a8d42dca3e9c852ef07f71fe3d1ebb0e4ceb0d2921 (SHA256) 0 0 Read More Popular Posts Since this is a very large change to the Ansible community package, I propose to slow this discussion down and not decide anything until very late in the Ansible 14 release cycle, or even just for 15.0.0 (or one of its pre-releases). This gives more interested parties (users, OS packagers, affected collection developers) time to take part in the discussion (if they want to). Felix Fontein felixfontein Proposal: trimming down the Ansible community package and collection removal roadmap Read More New for you Where to report feature request for ansible-galaxy client command? Get Help 1 1 Porting from Ansible 2.19 to 2.14: unsafe conditionals Get Help 0 0 New Release: ansible-core v2.20.11rc1 Ecosystem Releases 0 0 New Release: ansible-core v2.21.6rc1 Ecosystem Releases 0 0 New Release: ansible-core v2.19.15rc1 Ecosystem Releases 0 0 GitHub: github.com/ansible/ansible/releases/tag/v2.22.0rc2 full changelog: github.com/ansible/ansible/blob/v2.22.0rc2/change…

Opened a PR on @ansible: hardware fact gathering crashed with IndexError when lvs printed "Retrying metadata scan." to stdout, so ansible_mounts came back empty. The fix skips non-data lines in vgs/lvs/pvs output, with a unit test. ansible#87642 #Ansible

Opened a PR on @ansible: get_lvm_facts treated every line of vgs/lvs/pvs output as a data row, so an LVM notice like "Retrying metadata scan." raised an IndexError and broke hardware fact gathering. Now non-data lines are skipped, with a unit test. ansible#87642