Skip to content
This repository was archived by the owner on May 28, 2021. It is now read-only.
This repository was archived by the owner on May 28, 2021. It is now read-only.

Failed to get the cluster status: exit status 1 #293

Closed
@nataz77

Description

@nataz77

Is this a BUG REPORT or FEATURE REQUEST?

BUG REPORT

Versions

MySQL Operator Version: 0.3.0

Environment:

  • Kubernetes version (use kubectl version): 1.14.3
  • Cloud provider or hardware configuration: 4VM (2vCPU, 8GB) running in private cloud
  • OS (e.g. from /etc/os-release): Ubuntu 16.04
  • Kernel (e.g. uname -a): Linux 4.4.0-159-generic Use --decode for cross OS compatibility #187-Ubuntu SMP Thu Aug 1 16:28:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  • Others:

What happened?

I was trying to create a new cluster, but wherever the first pod starts, the agent throws an error and won't work correctly.

E1029 17:10:27.196303 1 cluster_manager.go:126] Failed to get the cluster status: exit status 1
getting cluster status from group seeds
github.com/oracle/mysql-operator/pkg/controllers/cluster/manager.(*ClusterManager).getClusterStatus
/go/src/github.com/oracle/mysql-operator/pkg/controllers/cluster/manager/cluster_manager.go:106
github.com/oracle/mysql-operator/pkg/controllers/cluster/manager.(*ClusterManager).Sync
/go/src/github.com/oracle/mysql-operator/pkg/controllers/cluster/manager/cluster_manager.go:122
github.com/oracle/mysql-operator/cmd/mysql-agent/app.Run
/go/src/github.com/oracle/mysql-operator/cmd/mysql-agent/app/mysql_agent.go:108
main.main
/go/src/github.com/oracle/mysql-operator/cmd/mysql-agent/main.go:51
runtime.main
/usr/local/go/src/runtime/proc.go:195
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:2337

What you expected to happen?

The correct startup of the cluster

How to reproduce it (as minimally and precisely as possible)?

  1. kubectl create ns dgitest
cat <<EOF | kubectl create -f -
apiVersion: mysql.oracle.com/v1alpha1
kind: Cluster
metadata:
  name: mysql
  namespace: dgitest
spec:
  imagePullPolicy: Always
  members: 1
  rootPasswordSecret:
    name: mysql-root-user-secret
  volumeClaimTemplate:
    metadata:
      name: data
    spec:
      storageClassName: sc-9899q
      accessModes:
        - ReadWriteMany
      resources:
        requests:
          storage: 10Gi
EOF

Anything else we need to know?

The storage class is based on GlusterFS and Heketi, and it's currenty able to provision new volumes correctly. Whenever I run the command above to deploy the cluster it creates the PVC correctly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions