Red Hat Bugzilla – Bug 1562943
CRI-O requires nodes labelled as "runtime=cri-o"
Last modified: 2018-04-02 22:01:38 EDT
Description of problem:
Version-Release number of the following components:
OCP 3.9 GA
Steps to Reproduce:
1. Try to install OCP with CRI-O support and Garbage Collection Support enabled
2. Install fails with a message that no nodes labelled "runtime=cri-o" are found
This is either an installer or a docs bug. Relevant Docs:
Docs say on "openshift_crio_enable_docker_gc":
When enabled, it will run garbage collection on all nodes by default. You can also limit the running of the daemonset on specific nodes by setting the following:
However this setting seems to be the default and if no nodes in the cluster are labelled as "runtime=cri-o" the install fails.
We already have a installer bug to track this:
For doc, there is some statement about it:
For example, the above would ensure it is only run on nodes with the runtime: cri-o label.
From QE's view, the statement is already clear.
Here I will close this bug as a DUP. If you still think the doc is not clear enough, pls reopen it, and move it to "Document" component. Thx.
*** This bug has been marked as a duplicate of bug 1553452 ***