Closed mrc0mmand closed 10 months ago
See also RHBZ 2235578
Hello, I ran into this issue.
I wanted to create a GCP instance using fedora 39.
I can hit this failure if I do dnf install openssl
.
I wanted to mention it here as it blocked me from continuing on to test with fedora 39. I hope there will be a release soon to fix this.
Hello @kannon92, the fix was released with tracer-1.0 and tracer-1.1 is in F39 for two months now https://bodhi.fedoraproject.org/updates/FEDORA-2023-924fcc46d1
Are you sure you are using the up-to-date version?
Hello @kannon92, the fix was released with tracer-1.0 and tracer-1.1 is in F39 for two months now https://bodhi.fedoraproject.org/updates/FEDORA-2023-924fcc46d1
Are you sure you are using the up-to-date version?
The main issue is I was using whatever GCP says they consider the latest.. I just wanted to report it because I didn't have control over the latest version of F39. I realized that it was considered beta in GCP so I decided to backtrack to F38 for my testing.
The image I used for GCP was Fedora Cloud Base 39_Beta 39-20230912.0.
Hey!
In one of our Rawhide CI jobs I noticed a traceback when running a transaction with dnf4 (a temporary workaround, since that particular transaction has issues with dnf5), and it can be easily reproduced with: