Comment 5 for bug 2046172

I'm actually not able to reproduce the issue. I've just spawned a Rocky host from latest image. On the first login `curl-minimal` was already installed. With that `dnf install /usr/bin/curl` is happy and does not claim any conflict.

[rocky@server-1212-1108 ~]$ sudo -s
[root@server-1212-1108 rocky]# dnf install /usr/bin/curl
Last metadata expiration check: 0:07:23 ago on Tue Dec 12 10:12:48 2023.
Package curl-minimal-7.76.1-26.el9_3.2.0.1.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
[root@server-1212-1108 rocky]#

And eventually ./scripts/bootstrap-aio.sh as well as bootstrap-ansible.sh pass nicely on master branch.

I've also tried a sample playbook that tries to install `/usr/bin/curl` using package module and it passed without raising any issues.

So in fact I am not able to reproduce the issue.

However, from what I see in your first output, you currently have `curl` installed - not `curl-minimal`. But I am pretty sure that Rocky 9.3 goes with `curl-minimal` out of the box.
So how you ended up with `curl` being installed there? Was it some older image upgraded with DNF to 9.3, like 9.1 or 9.0?

As I assume that this exact difference (of having curl instead of curl-minimal out of the box) what potentially leads to the issue.