Description of problem:
On 4.1.20 the logging operator is adding to nodeSelectors "kubernetes.io/os: linux" BUT not a single node has this label. They have "beta.kubernetes.io/os: linux".
In OSD we manage compute with Hive. Hive does not allow edits to labels.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Provision 4.1.20 cluster.
2. Attempt to configure ClusterLogging (https://docs.openshift.com/dedicated/4/logging/dedicated-efk-deploying.html)
Logging cannot be deployed.
Logging stack is deployed.
The docs for OSD do not include any variant of kubernetes.io/os label in the ClusterLogging CR. This is *added* by the logging operator. My workaround at this time is recreate compute w/ the expected label.
which channel did you install logging from? preview(which is 4.1) or 4.2?
(for a 4.1 cluster you should be installing from the preview channel).
Customers install the logging and elasticsearch operators from OperatorHub. The channel selected by default at this time is "4.2".
On this cluster it is "4.2".
$ oc get subscription -n openshift-logging cluster-logging -o yaml
please change the subscription to preview if you are installing in a 4.1 cluster.
We can pursue how to enforce this (OLM operators can specify a minimum kubeversion, sounds like the v4.2 logging operator should specify a minimum kubeversion that ensures it only gets installed on v4.2+ clusters), but manually choosing the correct channel should get you past this.
I have deleted the cluster-logging operator and installed from the "preview" channel and it works.
I hadn't tried selecting a specific channel before this and honestly wasn't sure what the UI allowed until I poked it. How does a customer know what version of an operator can be deployed on what version of OCP?
see my comment 5. I think we need to enforce a minKubeVersion in the logging operator to help avoid this problem in the future. We can use this bug to get that done.
also if the nodeselector in question was on the operand (not the operator) then we should definitely enhance the logging api to allow the user to set their own nodeselector on the operand (i.e. we should also fix that as part of resolving this bug)
> In OSD we manage compute with Hive. Hive does not allow edits to labels.
also it would be worth taking this up with the Hive team... i'd be interested to know if this is an intentional restriction in Hive, or a missing feature.
Maybe send a BZ/RFE their way also?
(In reply to Ben Parees from comment #8)
> also if the nodeselector in question was on the operand (not the operator)
> then we should definitely enhance the logging api to allow the user to set
> their own nodeselector on the operand (i.e. we should also fix that as part
> of resolving this bug)
You can define nodeselector in the CR but this one in particular is fixed and intentionally it is not possible to change it or override it
(In reply to Ben Parees from comment #7)
> see my comment 5. I think we need to enforce a minKubeVersion in the
> logging operator to help avoid this problem in the future. We can use this
> bug to get that done.
Do we know how to enforce?
It's a csv setting, Evan should be able to show you how to do it.
Please note that when installing Cluster Logging you must also be in the "openshift-logging" project and it is not enough to just select the "openshift-logging" namespace as described in the docs.
It is still minKubeVersion in CSV 4.3.0-201910311526. Waiting another image.
# The version value is substituted by the ART pipeline
displayName: Cluster Logging
The pr weren't merged to 4.3 branch.
This BZ is for the 4.3 branch which was merged here https://github.com/openshift/cluster-logging-operator/pull/263
Verified in 4.3, the Logging eventroute message can be gathered and transform to json
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.