Bug 1679130 - Cri-o installation method is not clear (manual rpm installation vs automatic installation)
Summary: Cri-o installation method is not clear (manual rpm installation vs automatic ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 3.11.z
Assignee: Ashley Hardin
QA Contact: Gaoyun Pei
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-20 12:17 UTC by gerodrig
Modified: 2022-03-13 17:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-20 13:56:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.