[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: The cluster-logging pods (Elasticsearch, Kibana, Fluentd) don't start - Openshift 4.1



Hi Jeff,
You're absolutely right. When I've edited the CSV cluster logging following Rich's procedure I got an error  for (minKubeVersion = 1.16.0) that say the requirements are not met.
When I revert back to  (minKubeVersion = 1.14.0), the error about requirement disaperaed but the pods are still in pending state.

When I labeled the nodes with ("beta.kubernetes.io/os: linux") as stated by Naveen Malik  in https://bugzilla.redhat.com/show_bug.cgi?id=1765261 
the pods are now running fine.

Thank you for your help.


-----Original Message-----
From: "Jeff Cantrill" [jcantril redhat com]
Date: 11/07/2019 09:11 AM
To: "Full Name" <haed98 excite com>
CC: "users lists openshift redhat com" <users lists openshift redhat com>, "Rich Megginson" <rmeggins redhat com>
Subject: Re: The cluster-logging pods (Elasticsearch, Kibana, Fluentd) don't
 start - Openshift 4.1





On Wed, Nov 6, 2019 at 6:48 PM Full Name <haed98 excite com> wrote:

Thank you Rich for your prompt reply.
 
 After viewing  the "manifests/4.2/cluster-logging.v4.2.0.clusterserviceversion.yaml " on the  cluster-logging-operator pod, I confirm that the added (minKubeVersion: 1.16.0) line in GITHUB  is missing in the manifest file on the CLO pod on my Cluster.


The minKubeVersion was corrected for 4.2 in: https://github.com/openshift/cluster-logging-operator/pull/267


 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]