strimzi-kafka-operator: Zookeeper Pod being killed, getting 'fsGroup: Invalid value'

On a local minishift instance with OKD 3.10 I can successfully bring up a cluster using 0.7.0 release. However, after the Zookeeper Pod dies for whatever reason, I’m getting the following events for the StatefulSet when trying to scale the Zookeeper StatefulSet back up:

create Pod avaf-dev-cluster-zookeeper-0 in StatefulSet avaf-dev-cluster-zookeeper failed error: pods "avaf-dev-cluster-zookeeper-0" is forbidden: unable to validate against any security context constraint: [fsGroup: Invalid value: []int64{1001}: 1001 is not an allowed group]

create Pod avaf-dev-cluster-zookeeper-0 in StatefulSet avaf-dev-cluster-zookeeper failed error: pods "avaf-dev-cluster-zookeeper-0" is forbidden: no providers available to validate pod request

screen shot 2018-09-28 at 16 54 12

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 19 (8 by maintainers)

Commits related to this issue

Most upvoted comments

Except one difference, the group that it says is invalid for me is 0:

create Pod my-cluster-zookeeper-0 in StatefulSet my-cluster-zookeeper failed error: pods "my-cluster-zookeeper-0" is forbidden: unable to validate against any security context constraint: [fsGroup: Invalid value: []int64{0}: 0 is not an allowed group]

We just had this issue today on OpenShift 4.5. It happened after an upgrade from OCP 4.5.14 to 4.5.15. It was our experimental cluster with no data, so we removed the whole Kafka setup and let ArgoCD deploy it all fresh, then it worked again. But if this happens on a cluster with users and data I don’t know what to do.

Since I haven’t received any further feedback, I will close this issue and assume it is fixed by the templating feature. In case this issue persists, feel free to re-open it or open a new one.