Bug 1699268

Summary: The kibana couldn't be scaled up when replicas=2 in clusterlogging CRD
Product: OpenShift Container Platform Reporter: Anping Li <anli>
Component: LoggingAssignee: ewolinet
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: aos-bugs, ewolinet, jcantril, qitang, rmeggins
Target Milestone: ---   
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-04 10:47:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Anping Li 2019-04-12 09:33:31 UTC
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:

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

Comment 1 ewolinet 2019-04-16 15:11:57 UTC
I am able to recreate this. Will investigate further for solution

Comment 4 Qiaoling Tang 2019-04-19 05:13:00 UTC
The .spec.replicas=2 in clusterlogging instance, but only one kibana pod is deployed.
$ oc get clusterlogging -o yaml

          resources: null
        replicas: 2
        resources: null
      type: kibana

      - deployment: kibana
          failed: []
          notReady: []
          - kibana-f5db689bd-xccsv
        - kibana-f5db689bd
        replicas: 1

CLO image: quay.io/openshift/origin-cluster-logging-operator@sha256:51f65deb0565f275b1eb34eb510596ef04c3f1c85daffab2b8be1e957f20f218

Comment 7 Qiaoling Tang 2019-05-05 01:32:42 UTC
Verified in quay.io/openshift/origin-cluster-logging-operator@sha256:c2988870f4f47617394e6510aca690ddf6ec448b2579c4829e7d34e67e1129ee.

Comment 9 errata-xmlrpc 2019-06-04 10:47:31 UTC
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.