cockroachdb / cockroachdb/cockroach-operator

Multiple cockroachdb-vcheck pods in pending state cause depoyment to fail

Open
#465 9 comments 0 reactions 1 assignee Claimed by @keith-mcclellan View on GitHub
bug
Dominant language
Go
Stars
318
Forks
104
Avg merge
1d 6h
Merged PRs (30d)
1

Description

Just tried deploying CRDB via the operator and hit an issue which blocked the deployment. The state looked like this:
```
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
cockroach-operator-64fb9fd497-b5gdh 1/1 Running 1 30m
cockroachdb-vcheck-26995099-522cz 0/1 Pending 0 23m
cockroachdb-vcheck-26995101-gkl5j 0/1 Pending 0 21m
cockroachdb-vcheck-26995104-kv8jh 0/1 Pending 0 18m
cockroachdb-vcheck-26995108-k9dq6 0/1 Pending 0 14m
cockroachdb-vcheck-26995116-phdz7 0/1 Completed 0 7m3s
```

After correcting the example.yaml file (I'd spec'd too much CPU/RAM), and they deleting it and re-applying it, I was able to proceed:
```
[mgoddard@MichaelG-MacBook-Pro Bug_Bash_2021.04.29]$ kubectl delete -f example.yaml
crdbcluster.crdb.cockroachlabs.com "cockroachdb" deleted
[mgoddard@MichaelG-MacBook-Pro Bug_Bash_2021.04.29]$ kubectl get pods
NAME READY STATUS RESTARTS AGE
cockroach-operator-64fb9fd497-b5gdh 1/1 Running 1 41m
[mgoddard@MichaelG-MacBook-Pro Bug_Bash_2021.04.29]$ kubectl apply -f example.yaml
crdbcluster.crdb.cockroachlabs.com/cockroachdb created
[mgoddard@MichaelG-MacBook-Pro Bug_Bash_2021.04.29]$ kubectl get pods
NAME READY STATUS RESTARTS AGE
cockroach-operator-64fb9fd497-b5gdh 1/1 Running 1 42m
cockroachdb-0 0/1 ContainerCreating 0 15s
cockroachdb-vcheck-26995134-6r4fh 1/1 Terminating 0 17s
[mgoddard@MichaelG-MacBook-Pro Bug_Bash_2021.04.29]$ kubectl get pods
NAME READY STATUS RESTARTS AGE
cockroach-operator-64fb9fd497-b5gdh 1/1 Running 1 42m
cockroachdb-0 1/1 Running 0 57s
cockroachdb-1 0/1 Running 0 27s
cockroachdb-vcheck-26995134-6r4fh 1/1 Terminating 0 59s
[mgoddard@MichaelG-MacBook-Pro Bug_Bash_2021.04.29]$ kubectl get pods
NAME READY STATUS RESTARTS AGE
cockroach-operator-64fb9fd497-b5gdh 1/1 Running 1 43m
cockroachdb-0 1/1 Running 0 115s
cockroachdb-1 1/1 Running 0 85s
cockroachdb-2 1/1 Running 0 55s
```

Apparently, there was one pending vcheck pod per each of my attempts to revise and reapply the YAML.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.