Troubleshooting
Problem
After installing or upgrading IBM AIOps, the aiops-topology-cassandra StatefulSet fails to create its pod on OpenShift. The StatefulSet controller repeatedly attempts to schedule aiops-topology-cassandra-0 but is blocked by the OpenShift Security Context Constraint (SCC) admission controller.
The Cassandra container image is built to run as UID/GID 1001. On OpenShift clusters with namespace-scoped UID ranges (typically 1000870000–1000879999), this hardcoded UID falls outside the permitted range. Additionally, the service account aiops-topology-service-account is not bound to any SCC that permits UID 1001 or fsGroup 1001, causing all available SCC providers to reject the pod.
Symptom
The following FailedCreate warning event is observed repeatedly on the StatefulSet:
Warning FailedCreate statefulset-controller
create Pod aiops-topology-cassandra-0 in StatefulSet aiops-topology-cassandra
failed error: pods "aiops-topology-cassandra-0" is forbidden: unable to validate
against any security context constraint:
[provider "anyuid": Forbidden: not usable by user or serviceaccount,
provider restricted-v2: .spec.securityContext.fsGroup: Invalid value:
[]int64{1001}: 1001 is not an allowed group,
provider restricted-v2: .initContainers[0].runAsUser: Invalid value:
1001: must be in the ranges: [1000870000, 1000879999],
provider restricted-v2: .containers[0].runAsUser: Invalid value:
1001: must be in the ranges: [1000870000, 1000879999],
...]
Cause
The root causes identified in the event are:
Violation | Detail |
| runAsUser: 1001 | UID 1001 is outside the namespace-allowed range [1000870000, 1000879999] |
| fsGroup: 1001 | GID 1001 is not an allowed supplemental/fs group in the namespace |
| hostUsers: null | restricted-v3 requires hostUsers explicitly set to false |
| Service account SCC binding missing | aiops-topology-service-account is not bound to any SCC permitting UID 1001 |
Additional observable symptoms:
- The pod
aiops-topology-cassandra-0is never created; it does not appear inoc get pods. - The StatefulSet shows
0/1ready replicas indefinitely. - Dependent AIOps topology services remain degraded or unavailable.
Resolving The Problem
Bind the anyuid SCC to the aiops-topology-service-account service account in the IBM AIOps namespace. This permits the Cassandra container to run as UID 1001 as intended by the image.
Identify the IBM AIOps namespace (if unknown):
oc get subscriptions -A | grep aiops
Note the namespace from the output and use it in place of <NAMESPACE> in all subsequent commands.
Confirm the service account name:
oc get statefulset aiops-topology-cassandra -n <NAMESPACE> \ -o jsonpath='{.spec.template.spec.serviceAccountName}'Expected output:
aiops-topology-service-accountGrant the
anyuidSCC to the service account:oc adm policy add-scc-to-user anyuid \ -z aiops-topology-service-account \ -n <NAMESPACE>
Restart the StatefulSet to trigger pod re-creation:
oc rollout restart statefulset/aiops-topology-cassandra -n <NAMESPACE>
Verify the pod starts successfully:
oc get pods -n <NAMESPACE> -w | grep cassandra
Wait for
aiops-topology-cassandra-0to reachRunningstatus.Confirm the correct SCC was applied to the running pod:
oc get pod aiops-topology-cassandra-0 -n <NAMESPACE> \ -o jsonpath='{.metadata.annotations.openshift\.io/scc}'Expected output:
anyuid
aiops-topology-cassandra StatefulSet is managed by the IBM AIOps operator, the operator may reconcile and overwrite service account bindings during upgrades or restarts. Re-run the add-scc-to-user command after any operator reconciliation cycle if the issue recurs.Document Location
Worldwide
Product Synonym
IBM Cloud Pak for AIOps, AIOps, CP4AIOps
Was this topic helpful?
Document Information
Modified date:
08 August 2026
UID
ibm17283037