P.S. coreutils which contains sha256sum is already installed, so that's not a problem.
When do you need this? (YYYY/MM/DD) Before 2025/03/13 (the next Go/No-Go date).
When is this no longer needed or useful? (YYYY/MM/DD) There will always be new candidates so it would be nice if isomd5sum could be permanently added to the list of installed packages.
If we cannot complete your request, what is the impact? Possibly not being able to do the checksum tests, unless I can find an executable that runs on RHEL9. Even if I can I don't think it's good to run tests that way.
I put back the executable from isomd5sum-1.2.3-3.el8.x86_64.rpm from CentOS 8 (which is the old RPM I was using before) and it still appears to run. So I'm probably okay but nevertheless it would be better to run these tests using the official isomd5sum package.
Metadata Update from @phsmoura: - Issue tagged with: high-trouble, low-gain, ops
I wasn't sure, if it's the right place to add the package, but I tried opening a PR: https://pagure.io/fedora-infra/ansible/pull-request/2521#, I'll let @kevin or ansible experts review this, and then we can run the playbook to test it out!
Yep. thats exactly the right place. ;)
Thanks!
Metadata Update from @kevin: - Issue assigned to jnsamyak - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Thanks for doing this! I just logged into secondary01 and saw that the isomd5sum package was installed at "Wed 19 Mar 2025 09:28:55 PM UTC" (rpm -qi output). From the pull request link above I thought that it had failed, it shows two "Build failed" errors.
Yeah, those are CI checks. They were siliently broken for a long time (always reporting success), so we need to do more to get things back to where they actually report problems on new PR's. ;( Anyhow, it should be installed.
Log in to comment on this ticket.