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

Bug 1680278

Summary: Upgrade fails in environments with cri-o
Product: OpenShift Container Platform Reporter: Borja Aranda <farandac>
Component: InstallerAssignee: Scott Dodson <sdodson>
Installer sub component: openshift-ansible QA Contact: Johnny Liu <jialiu>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: high    
Version: 3.10.0   
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: 2019-02-25 13:36:21 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 2019-02-23 15:07:14 UTC 
Description of problem:

Upgrade from 3.9.65 to the latest errata 3.10.111 fails in an image check:
~~~
# crictl images -q registry.access.redhat.com/openshift3/ose-node:v3.10

W0222 15:11:37.682236  120944 util_unix.go:75] Using "/var/run/crio/crio.sock" as endpoint is deprecated, please consider using full url format "unix:///var/run/crio/crio.sock".
FATA[0000] listing images failed: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.ImageService
~~~

The rpc error is generated apparently because the playbook installs cri-tools-1.0.0-5.rhaos3.10.git2e22a75.el7.x86_64, and the cri-o version in the node is still cri-o-1.9.14-1.git4e220eb.el7.x86_64

The ImageService should be served by the crio.sock and consumed by kubelet and crictl, but it seems to be incompatible between versions.


Version-Release number of the following components:
upgrade from 3.9.65 to openshift-ansible 3.10.111
Comment 2 Scott Dodson 2019-02-25 13:36:21 UTC 
No they're not compatible.

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