Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: After upgrading cri-o1.36 from 1.36.4-3.fc44 to 1.36.5-1.fc44, crio.service fails to start. The pinns binary was moved from /usr/bin/pinns to /usr/libexec/crio/pinns, but CRI-O still searches for it in $PATH, causing a fatal validation error. Version-Release number of selected component (if applicable): cri-o1.36-1.36.5-1.fc44 How reproducible: Always. Steps to Reproduce: 1.On Fedora CoreOS 44 with rpm-ostree layered packages cri-o1.36 and kubernetes1.36, upgrade cri-o1.36 from 1.36.4-3.fc44 to 1.36.5-1.fc44 2.Reboot 3.Check systemctl status crio and journalctl -u crio Actual results: crio.service fails with: ```text level=fatal msg="validating runtime config: pinns validation: exec: \"pinns\": executable file not found in $PATH" ``` `rpm -ql cri-o1.36 | grep pinns` shows `/usr/libexec/crio/pinns` in 1.36.5, while the old 1.36.4 RPM had `/usr/bin/pinns`. Expected results: crio.service starts successfully. Additional info: Old package: cri-o1.36-1.36.4-3.fc44.x86_64.rpm → /usr/bin/pinns New package: cri-o1.36-1.36.5-1.fc44 → /usr/libexec/crio/pinns Workaround: rollback to 1.36.4.
Thanks for the report. I will check and resolve.
Was able to work around with drop-in file /etc/crio/crio.conf.d/10-pinns.conf with the following contents: [crio.runtime] pinns_path = "/usr/libexec/crio/pinns"
FEDORA-2026-05f65b07d7 (cri-o1.36-1.36.6-1.fc46) has been submitted as an update to Fedora 46. https://bodhi.fedoraproject.org/updates/FEDORA-2026-05f65b07d7
FEDORA-2026-05f65b07d7 (cri-o1.36-1.36.6-1.fc46) has been pushed to the Fedora 46 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-77abfa2cdd (cri-o1.36-1.36.6-1.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-77abfa2cdd
FEDORA-2026-f5c88f763a (cri-o1.36-1.36.6-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-f5c88f763a
FEDORA-2026-0025579bc9 (cri-o1.36-1.36.6-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-0025579bc9
FEDORA-2026-77abfa2cdd has been pushed to the Fedora 45 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-77abfa2cdd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-77abfa2cdd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-f5c88f763a has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-f5c88f763a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-f5c88f763a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-0025579bc9 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-0025579bc9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-0025579bc9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-f5c88f763a (cri-o1.36-1.36.6-1.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-0025579bc9 (cri-o1.36-1.36.6-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-77abfa2cdd (cri-o1.36-1.36.6-1.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.