Cluster setup failed: failed to run pod:

i fail to setup a CB cluster on Openshift 4.1 with the cb operator 1.1 from the operator hub.
In the operator log I only find the following hint:

time=“2019-08-07T11:29:40Z” level=error msg="Cluster setup failed: failed to run pod: " cluster-name=myspace module=cluster
time=“2019-08-07T11:29:40Z” level=warning msg=“Fail to handle event: ignore failed cluster (myspace). Please delete its CR”

clusterconf:

apiVersion: couchbase.com/v1
kind: CouchbaseCluster
metadata:
creationTimestamp: ‘2019-08-07T11:29:30Z’
generation: 5
name: myspace
namespace: myspace-cb
resourceVersion: ‘12540618’
selfLink: /apis/couchbase.com/v1/namespaces/myspace-cb/couchbaseclusters/myspace
uid: 9f0c4101-b906-11e9-ac6c-020004eb0006
spec:
adminConsoleServices:
- data
baseImage: registry.connect.redhat.com/couchbase/server
exposeAdminConsole: true
servers:
- name: all_services
pod:
resources: {}
volumeMounts:
default: cb
services:
- data
- index
- query
- search
size: 2
disableBucketManagement: true
volumeClaimTemplates:
- metadata:
creationTimestamp: null
name: cb
spec:
resources:
requests:
storage: 10Gi
storageClassName: local
status: {}
version: 6.0.2-1
softwareUpdateNotifications: false
authSecret: cb-admin
cluster:
autoFailoverTimeout: 10
autoFailoverOnDataDiskIssues: true
clusterName: myspace
indexStorageSetting: memory_optimized
analyticsServiceMemoryQuota: 1024
eventingServiceMemoryQuota: 256
searchServiceMemoryQuota: 256
autoFailoverMaxCount: 3
dataServiceMemoryQuota: 256
autoFailoverOnDataDiskIssuesTimePeriod: 120
indexServiceMemoryQuota: 256
autoFailoverServerGroup: false
exposedFeatures:
- xdcr

Storage Class Config:

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: local
selfLink: /apis/storage.k8s.io/v1/storageclasses/local
uid: b819edb4-a3d4-11e9-b1ee-0200100f0005
resourceVersion: ‘690312’
creationTimestamp: ‘2019-07-11T12:09:22Z’
annotations:
description: local_PV
provisioner: kubernetes.io/no-provisioner
reclaimPolicy: Retain
volumeBindingMode: WaitForFirstConsumer

Does anyone have any idea what I’m doing wrong?
Regards Daniel

Ah, 1.1… If you could upgrade to 1.2 that would be better as it will dump out the failed Pod’s YAML and have more context e.g. what state it was in, why it wasn’t provisioning etc.

However, if this isn’t an option you will need to manually poll kubectl describe pod/myspace-0000 (before the operator deletes it) to see why it isn’t running correctly.

Hi Simon
Thanks for your Answer. Is the 1.2 Operator supported in OpenShift 4.1?

To be honest we’ve done no testing on 4.1 as it’s so new. Operator 2.0.0 will support 4.1 as its core platform, but that’s not out until next year. Given things are mostly backwards compatible it should work…

In the mean time I’d certainly be interested to see how you get on with it and give you a hand getting it to work.