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

Bug 1679130

Summary: Cri-o installation method is not clear (manual rpm installation vs automatic installation)
Product: OpenShift Container Platform Reporter: gerodrig
Component: DocumentationAssignee: Ashley Hardin <ahardin>
Status: CLOSED CURRENTRELEASE QA Contact: Gaoyun Pei <gpei>
Severity: low Docs Contact: Vikram Goyal <vigoyal>
Priority: low    
Version: 3.11.0CC: aos-bugs, cnegus, djuran, jokerman, mmccomas, wsun
Target Milestone: ---   
Target Release: 3.11.z   
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: 2020-04-20 13:56:15 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 gerodrig 2019-02-20 12:17:57 UTC 
Document URL: 

https://access.redhat.com/documentation/en-us/openshift_container_platform/3.11/html-single/cri-o_runtime/

Section Number and Name: 

1.2. Getting CRI-O

Describe the issue:

The documentation is not very clear whether cri-o should be installed via rpm or if the installer is going to take care of it.

The issue is that installing it via a rpm causes an error [1], and doing so is not a supported operation.


Suggestions for improvement: 

Make more clear/explicit that you should let the installer install cri-o and that it shouldn't be installed via rpm.


Additional information:

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1636493
Comment 4 Ashley Hardin 2020-04-16 19:34:18 UTC 
Work in progress: https://github.com/openshift/openshift-docs/pull/21236
Comment 5 Gaoyun Pei 2020-04-17 09:32:21 UTC 
The proposed PR lgtm, move it to verified.
Comment 6 Ashley Hardin 2020-04-20 13:56:15 UTC 
Content is now published: https://access.redhat.com/documentation/en-us/openshift_container_platform/3.11/html/cri-o_runtime/use-crio-engine#get-crio-use-crio-engine