Bug 2540885

Summary: cri-o 1.36.5: pinns moved to /usr/libexec/crio, crio fails to start
Product: [Fedora] Fedora Reporter: Junjie Yuan <yuan>
Component: cri-o1.36Assignee: Brad Smith <bradley.g.smith>
Status: CLOSED ERRATA QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 44CC: bradley.g.smith, go-sig, leonid
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: cri-o1.36-1.36.6-1.fc46 cri-o1.36-1.36.6-1.fc44 cri-o1.36-1.36.6-1.fc43 cri-o1.36-1.36.6-1.fc45 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-09-27 21:13:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Junjie Yuan 2026-09-25 01:24:47 UTC
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.

Comment 1 Brad Smith 2026-09-25 23:51:53 UTC
Thanks for the report. I will check and resolve.

Comment 2 Leonid Podolny 2026-09-26 01:14:01 UTC
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"

Comment 3 Fedora Update System 2026-09-27 21:09:16 UTC
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

Comment 4 Fedora Update System 2026-09-27 21:13:43 UTC
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.

Comment 5 Fedora Update System 2026-09-27 21:24:46 UTC
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

Comment 6 Fedora Update System 2026-09-27 21:43:44 UTC
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

Comment 7 Fedora Update System 2026-09-27 21:58:59 UTC
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

Comment 8 Fedora Update System 2026-09-28 01:48:57 UTC
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.

Comment 9 Fedora Update System 2026-09-28 02:07:52 UTC
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.

Comment 10 Fedora Update System 2026-09-28 02:30:54 UTC
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.

Comment 11 Fedora Update System 2026-10-05 01:06:34 UTC
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.

Comment 12 Fedora Update System 2026-10-05 01:24:46 UTC
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.

Comment 13 Fedora Update System 2026-10-06 00:16:57 UTC
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.