Hide Forgot
Description of problem: deploy cluster logging when replicas=2 for kibana, the replicas is still 1 in deployment/kibana. Version-Release number of selected component (if applicable): image: quay.io/openshift/origin-cluster-logging-operator:latest imageID: quay.io/openshift/origin-cluster-logging-operator@sha256:51f65deb0565f275b1eb34eb510596ef04c3f1c85daffab2b8be1e957f20f218 How reproducible: Always Steps to Reproduce: 1. deploy cluster logging using replcias=2 for kibbana oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/logging/clusterlogging/customresource-fluentd.yaml 2. check the replicas number in deployment/kibana oc get deployment/kibana -o jsonpath={.spec.replicas} Actual results: The .spec.replicas=1 Expected results: The .spec.replicas=2
I am able to recreate this. Will investigate further for solution
https://github.com/openshift/cluster-logging-operator/pull/157
The .spec.replicas=2 in clusterlogging instance, but only one kibana pod is deployed. $ oc get clusterlogging -o yaml visualization: kibana: proxy: resources: null replicas: 2 resources: null type: kibana visualization: kibanaStatus: - deployment: kibana pods: failed: [] notReady: [] ready: - kibana-f5db689bd-xccsv replicaSets: - kibana-f5db689bd replicas: 1 CLO image: quay.io/openshift/origin-cluster-logging-operator@sha256:51f65deb0565f275b1eb34eb510596ef04c3f1c85daffab2b8be1e957f20f218
Verified in quay.io/openshift/origin-cluster-logging-operator@sha256:c2988870f4f47617394e6510aca690ddf6ec448b2579c4829e7d34e67e1129ee.
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. https://access.redhat.com/errata/RHBA-2019:0758