Bug 1664941
| Summary: | Deploy logging failed at "spec.logStore.elasticsearch.replicas in body is required" | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qiaoling Tang <qitang> |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
| Status: | CLOSED NOTABUG | QA Contact: | Anping Li <anli> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | aos-bugs, rmeggins |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-01-25 14:49:36 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: | |
| Embargoed: | |||
| Bug Depends On: | 1666944 | ||
| Bug Blocks: | |||
|
Description
Qiaoling Tang
2019-01-10 06:13:28 UTC
$ oc get elasticsearches.logging.openshift.io -o yaml
apiVersion: v1
items:
- apiVersion: logging.openshift.io/v1alpha1
kind: Elasticsearch
metadata:
creationTimestamp: 2019-01-10T05:51:23Z
generation: 1
name: elasticsearch
namespace: openshift-logging
ownerReferences:
- apiVersion: logging.openshift.io/v1alpha1
controller: true
kind: ClusterLogging
name: qitang
uid: c29cc7d7-149b-11e9-b880-06c7e20fdb6a
resourceVersion: "155882"
selfLink: /apis/logging.openshift.io/v1alpha1/namespaces/openshift-logging/elasticsearches/elasticsearch
uid: c33ab78c-149b-11e9-b91a-0282b3a38dc0
spec:
managementState: Managed
nodeSpec:
image: docker.io/openshift/origin-logging-elasticsearch5:latest
resources: {}
nodes:
- nodeCount: 1
nodeSpec:
resources: {}
roles:
- client
- data
- master
storage: {}
redundancyPolicy: SingleRedundancy
status:
clusterHealth: yellow
conditions:
- lastTransitionTime: 2019-01-10T05:51:24Z
status: "True"
type: ScalingUp
- lastTransitionTime: 2019-01-10T05:51:26Z
message: Config Map is up to date
reason: ConfigChange
status: "False"
type: UpdatingSettings
- lastTransitionTime: 2019-01-10T05:51:26Z
status: "False"
type: ScalingDown
- lastTransitionTime: 2019-01-10T05:51:26Z
status: "False"
type: Restarting
nodes:
- deploymentName: elasticsearch-clientdatamaster-0-1
podName: elasticsearch-clientdatamaster-0-1-84d764899d-w9cq4
replicaSetName: elasticsearch-clientdatamaster-0-1-84d764899d
roles:
- client
- data
- master
status: Running
upgradeStatus:
underUpgrade: "False"
pods:
client:
failed: []
notReady: []
ready:
- elasticsearch-clientdatamaster-0-1-84d764899d-w9cq4
data:
failed: []
notReady: []
ready:
- elasticsearch-clientdatamaster-0-1-84d764899d-w9cq4
master:
failed: []
notReady: []
ready:
- elasticsearch-clientdatamaster-0-1-84d764899d-w9cq4
shardAllocationEnabled: "True"
kind: List
metadata:
resourceVersion: ""
selfLink: ""
This should be resolved once https://github.com/operator-framework/operator-lifecycle-manager/pull/655 merges. You are using whats checked into OLM which is not yet in sync with the changes made to clusterlogging That is not a test block. We can still deploy logging following following https://github.com/openshift/cluster-logging-operator Deployable as a community operator via https://github.com/operator-framework/community-operators/pull/16 which supersedes OLM. Additionally, must use the current CR which can be spec'd via: https://github.com/openshift/cluster-logging-operator/blob/master/docs/configuration.md#configuring-and-tuning-cluster-logging Closing this issue as NOTABUG as the spec is not valid anylonger because of the change referenced in #c4. Bug 1666944 encompasses the issue identified here. |