Container getting in to crashLoopBackOff status when tried from the tag 22.1.1 to 22.2.14
Dheena-TW opened this issue · comments
While trying helm upgrade on cockroachdb facing the below issue:
We are using this chart for different teams, and when we upgrade from 22.1.1 to 22.2.14 we didn't come across this issue on the other cockroach DB's, but only for one of the DB we are facing this issue.
Don't see much logs in the container, don't have a clue whats stopping where. Below is the log from the container
++ hostname
- exec /cockroach/cockroach start --join=cockroachdb-0.cockroachdb.teamc.svc.cluster.local:26257,cockroachdb-1.cockroachdb.teamc.svc.cluster.local:26257,cockroachdb-2.cockroachdb.promo.svc.cluster.local:26257 --advertise-host=cockroachdb-2.cockroachdb.promo.svc.cluster.local --insecure --http-port=8080 --port=26257 --cache=25% --max-sql-memory=25% --logtostderr=INFO
Flag --logtostderr has been deprecated, use --log instead to specify 'sinks: {stderr: {filter: ...}}'.
After this pod getting restarting and went to to crashLoopBackOff.
Any direction or suggestions are highly appreciated.
Fixed with diff chart version