Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1605166

Summary:	kubelet unable to run with cri-o 1.9.13
Product:	OpenShift Container Platform	Reporter:	Borja Aranda <farandac>
Component:	Containers	Assignee:	Mrunal Patel <mpatel>
Status:	CLOSED DUPLICATE	QA Contact:	DeShuai Ma <dma>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.9.0	CC:	aos-bugs, jokerman, mmccomas, wkulhane
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-20 13:17:32 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 Borja Aranda 2018-07-20 10:47:32 UTC

- Description of problem:
kubelet cannot start using cri-o 1.9.13 as container runtime

remote_runtime.go:69] Version from runtime service failed: rpc error: code = Unimplemented desc = unknown service runtime.RuntimeService

kuberuntime_manager.go:172] Get runtime version failed: rpc error: code = Unimplemented desc = unknown service runtime.RuntimeService

server.go:173] failed to run Kubelet: failed to create kubelet: rpc error: code = Unimplemented desc = unknown service runtime.RuntimeService

- Workaround:
Downgrade cri-o to 1.9.11 or exclude it in yum.conf before upgrading the OS

- Version-Release number of selected component (if applicable):
OCP 3.9.33
1.9.13-1.git52a8e70.el7
RHEL 7.5

How reproducible:
- Upgrade or install a fresh OCP cluster using cri-o as container runtime
- Update to the latest errata the SO (it contains cri-o 1.9.13)

- Actual results:
kubelet returns a fatal error and it can't start.

Comment 2 Wolfgang Kulhanek 2018-07-20 11:25:33 UTC

It appears on top of that the prerequisites playbooks pull the cri-o:latest image instead of cri-o:release

2018-07-20 11:16:19,003 p=18152 u=root |  ok: [support1.muc.internal] => {
    "l_crio_image": "registry.access.redhat.com/openshift3/cri-o:latest"
}
2018-07-20 11:16:19,009 p=18152 u=root |  ok: [support2.muc.internal] => {
    "l_crio_image": "registry.access.redhat.com/openshift3/cri-o:latest"

Comment 3 Wolfgang Kulhanek 2018-07-20 11:30:10 UTC

Which means this now also breaks releases earlier than 3.9.33 like 3.9.31...

Comment 4 Scott Dodson 2018-07-20 13:17:32 UTC


*** This bug has been marked as a duplicate of bug 1599605 ***