# Stuck between a bug and behaviour change

**URL:** <https://forum.ansible.com/t/stuck-between-a-bug-and-behaviour-change/40279>\
**Category:** Get Help\
**Tags:** rhel, aws\
**Created:** [February 14, 2025, 4:21pm UTC](https://forum.ansible.com/t/stuck-between-a-bug-and-behaviour-change/40279 "2025-02-14T16:21:17Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![UNiXMIT](https://avatars.discourse-cdn.com/v4/letter/u/e9a140/32.png) [@UNiXMIT](https://forum.ansible.com/u/UNiXMIT)\
**Post date:** [February 14, 2025, 4:21pm UTC](https://forum.ansible.com/t/stuck-between-a-bug-and-behaviour-change/40279/1 "2025-02-14T16:21:17Z")

</div>

Recently I became aware of this ’ [Newer versions of Ansible don’t work with RHEL 8](https://www.jeffgeerling.com/blog/2024/newer-versions-ansible-dont-work-rhel-8)’  
So I remained using ansible-core\<2.17  
But now I notice that i686 packages are not installed - [ansible.builtin.dnf doesn’t install i686 packages #83406](https://github.com/ansible/ansible/issues/83406)

So really my only choice, as I see it, is to drop support for RHEL 8. Does anyone know of another solution?

Thank you

---

<div class="post-metadata">

**Author:** ![bcoca](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bcoca/32/9269_2.png) [@bcoca](https://forum.ansible.com/u/bcoca)\
**Post date:** [February 14, 2025, 5:06pm UTC](https://forum.ansible.com/t/stuck-between-a-bug-and-behaviour-change/40279/2 "2025-02-14T17:06:49Z")

</div>

The fix [[stable-2.16] dnf - arches must be the same in the is\_newer\_installed check (#83417) by mkrizek · Pull Request #83505 · ansible/ansible · GitHub](https://github.com/ansible/ansible/pull/83505) was backported to 2.16

---

<div class="post-metadata">

**Author:** ![dnmvisser](https://avatars.discourse-cdn.com/v4/letter/d/8e8cbc/32.png) [@dnmvisser](https://forum.ansible.com/u/dnmvisser)\
**Post date:** [February 14, 2025, 5:13pm UTC](https://forum.ansible.com/t/stuck-between-a-bug-and-behaviour-change/40279/3 "2025-02-14T17:13:56Z")

</div>

If ansible-core\<2.17 works, I’d stay on that.  
It depends on your situation of course, but it may well be that a newer OS will cause a magnitude more work than a newer ansible version.  
I tend to run a reasonably recent version of ansible, but ansible isn’t used at runtime, only to deploy a system.  
So while currently EOL, I wouldn’t consider it a huge problem to use ansible-core 2.16 while I’m investigating/preparing an OS upgrade…

---

<div class="post-metadata">

**Author:** ![dnmvisser](https://avatars.discourse-cdn.com/v4/letter/d/8e8cbc/32.png) [@dnmvisser](https://forum.ansible.com/u/dnmvisser)\
**Post date:** [February 14, 2025, 5:17pm UTC](https://forum.ansible.com/t/stuck-between-a-bug-and-behaviour-change/40279/4 "2025-02-14T17:17:57Z")

</div>

> So while currently EOL, I wouldn’t consider it a huge problem to use ansible-core 2.16 while I’m investigating/preparing an OS upgrade…

This is basically what it says at the bottom of [https://www.jeffgeerling.com/blog/2024/newer-versions-ansible-dont-work-rhel-8](https://www.jeffgeerling.com/blog/2024/newer-versions-ansible-dont-work-rhel-8):

---

<div class="post-metadata">

**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\
**Post date:** [February 14, 2025, 5:46pm UTC](https://forum.ansible.com/t/stuck-between-a-bug-and-behaviour-change/40279/5 "2025-02-14T17:46:14Z")

</div>

> [@bcoca](#):
>
> The fix [[stable-2.16] dnf - arches must be the same in the is\_newer\_installed check (#83417) by mkrizek · Pull Request #83505 · ansible/ansible · GitHub](https://github.com/ansible/ansible/pull/83505) was backported to 2.16

@UNiXMIT To be specific, this fix should have been backported to 2.16.9. You may be using an older version, especially if you’re installing from AppStream instead of pip.

---

<div class="post-metadata">

**Author:** ![UNiXMIT](https://avatars.discourse-cdn.com/v4/letter/u/e9a140/32.png) [@UNiXMIT](https://forum.ansible.com/u/UNiXMIT)\
**Post date:** [February 14, 2025, 6:41pm UTC](https://forum.ansible.com/t/stuck-between-a-bug-and-behaviour-change/40279/6 "2025-02-14T18:41:37Z")

</div>

That’s fantastic. I’ll check what version I’m using and update it accordingly. Thank you.

---

<div class="post-metadata">

**Author:** ![UNiXMIT](https://avatars.discourse-cdn.com/v4/letter/u/e9a140/32.png) [@UNiXMIT](https://forum.ansible.com/u/UNiXMIT)\
**Post date:** [February 14, 2025, 7:12pm UTC](https://forum.ansible.com/t/stuck-between-a-bug-and-behaviour-change/40279/7 "2025-02-14T19:12:01Z")

</div>

Hmmm I’m running ansible-core 2.16.14  
I hope the bug hasn’t returned. But for sure it’s not installing any i686 versions that I’m telling it to install. Don’t get any errors from it either. I only find out at the end when I try to install something that requires it.

---

<div class="post-metadata">

**Author:** ![UNiXMIT](https://avatars.discourse-cdn.com/v4/letter/u/e9a140/32.png) [@UNiXMIT](https://forum.ansible.com/u/UNiXMIT)\
**Post date:** [February 18, 2025, 9:09am UTC](https://forum.ansible.com/t/stuck-between-a-bug-and-behaviour-change/40279/8 "2025-02-18T09:09:06Z")

</div>

Yeah it definitely doesn’t install i686 packages using 2.16.14 so I’ve dropped support for RHEL 8. Now that I’m on 2.18.2 it’s working OK.

---

<div class="post-metadata">

**Author:** ![shertel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/shertel/32/1241_2.png) [@shertel](https://forum.ansible.com/u/shertel)\
**Post date:** [February 18, 2025, 12:00pm UTC](https://forum.ansible.com/t/stuck-between-a-bug-and-behaviour-change/40279/9 "2025-02-18T12:00:58Z")

</div>

Please file a [bug report](https://github.com/ansible/ansible/issues/new?template=bug_report.yml). FWIW, 2.16.14 is successfully installing _this_ i686 package in the test, so it must not cover your reproducer [dnf - arches must be the same in the is\_newer\_installed check (#83417… · ansible/ansible@58b22a3 · GitHub](https://github.com/ansible/ansible/commit/58b22a3476a0fddd976aae9ff32710c54623e8d5#diff-ca105ad45f8493b6a4c0f1c7ebdaa6acabc00f54b7ad6724c0facd6c8c3ce0eaR425).