-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17.z, 4.18.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
OCP Node Sprint 276 (blue), OCP Node Sprint 277 (blue)
-
2
-
Customer Escalated
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When the gpg verification is enabled, the Image pull process with CRI-O is failing with panic which points to some issue with the libgpg verification.
Details:
cri-o-1.30.10-8.rhaos4.17.gite22f6d2.el9.x86_64 package installed
Default policy is "Reject" . F(dlv) p ("github.com/cri-o/cri-o/server.pullOperation")(0xc0021a4ed0)
github.com/cri-o/cri-o/server.pullOperation {
wg: sync.WaitGroup {
noCopy: sync.noCopy {},
state: (*"sync/atomic.Uint64")(0xc0021a4ed0),
sema: 0,},
imageRef: "",
err: error(*errors.errorString) *
,}
Please checkout comments below
- is blocked by
-
RHEL-99339 GPGME Mechanism Causing gpg-agent Process Stuck Issue
-
- New
-