Bug 2123412 - crio occasionally fails to start during deployment [Infra Operator tracking bz]
Summary: crio occasionally fails to start during deployment [Infra Operator tracking bz]
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Infrastructure Operator
Version: rhacm-2.6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Michael Filanov
QA Contact: Chad Crum
Derek
URL:
Whiteboard:
Depends On: 2099794 2132059 2132282
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-01 15:22 UTC by Chad Crum
Modified: 2022-11-06 08:49 UTC (History)
23 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2099794
Environment:
Last Closed: 2022-11-06 08:49:10 UTC
Target Upstream Version:
Embargoed:
ccrum: Blocker+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 25509 0 None None None 2022-09-01 18:38:45 UTC
Red Hat Issue Tracker MGMTBUGSM-546 0 None None None 2022-09-01 15:32:03 UTC

Comment 2 Chad Crum 2022-09-01 15:42:38 UTC 
Latest status is that 4.12 has a possible fix which must be verified before 4.11 backport can happen.

Sasha tested the 4.12 fix but the issue is still occurring.
Comment 4 Alexander Chuzhoy 2022-09-27 21:14:41 UTC 
The issue reproduced with:

VERSION="411.86.202209211811-0"

PRETTY_NAME="Red Hat Enterprise Linux CoreOS 411.86.202209211811-0 (Ootpa)"
OPENSHIFT_VERSION="4.11"
RHEL_VERSION="8.6"
OSTREE_VERSION="411.86.202209211811-0"
Comment 5 Michael Filanov 2022-11-03 08:41:41 UTC 
@sasha can you please open an OCPBUG on the crio  team?
Note You need to log in before you can comment on or make changes to this bug.