RunAI Troubleshooting

oc adm policy who-can use scc/runai-openshift-s3

- `system:authenticated`
- `system:serviceaccounts`
- `system:serviceaccounts:<namespace>`
- `system:serviceaccount:<namespace>:default`

oc adm policy remove-scc-from-user runai-openshift-s3 -z default -n <namespace>
# If it was granted to all service accounts in a namespace, remove it from the group instead:
oc adm policy remove-scc-from-group runai-openshift-s3 system:serviceaccounts:<namespace>

# Bind runai-openshift-s3 only to a dedicated Run:AI service account (not default), and ensure only the Run:AI controller and its workloads use that service account. This limits which workloads can effectively run with root-equivalent privileges.

#Please provide screenshots so we can see which page you are referring to where the limits are not showing.We also request that you send us a set of cluster logs.

curl -s https://raw.githubusercontent.com/runai-professional-services/log-collector/refs/heads/main/cluster.sh | bash

# Are you experiencing any issues creating projects within this cluster? I found a previous case that mentioned the "Error: Invalid input syntax for type bigint keycloak" may be due to errors during, or an incomplete upgrade process.

#For next steps, can you confirm that the backend upgrade completed succesfully with the following comand?
helm list -n runai-backend

#Additionally, if possible please share the backend and cluster logs file created by this script. Note: it requires the kubectl command.
curl -s https://raw.githubusercontent.com/runai-professional-services/log-collector/refs/heads/main/cluster.sh | bash

oc -n runai-backend exec -it runai-backend-postgresql-0 -- \
    env PGPASSWORD=<password> pg_dump -U postgres backend > cluster_name_db_backup.sql