Bug ID 1670353: Add the RabbitMQ serviceAccount to the Project’s privileged security context constraint (SCC)

Last Modified: Dec 21, 2025

Affected Product(s):
BIG_IP_NEXT(CNF) CNF(all modules)

Known Affected Versions:
1.3.1, 1.3.2, 1.3.3

Opened: Sep 13, 2024

Severity: 3-Major

Symptoms

RabbitMQ fails to start and reports an error Error creating: pods "f5-rabbit-77f9869445-" is forbidden: unable to validate against any security context constraint: [provider "anyuid": Forbidden: not usable by user or serviceaccount, provider restricted-v2: .containers[0].runAsUser: Invalid value: 2000: must be in the ranges: [1000940000, 1000949999], provider "restricted": Forbidden: not usable by user or serviceaccount, provider "nonroot-v2": Forbidden: not usable by user or serviceaccount, provider "nonroot": Forbidden: not usable by user or serviceaccount, provider "hostmount-anyuid": Forbidden: not usable by user or serviceaccount, provider "machine-api-termination-handler": Forbidden: not usable by user or serviceaccount, provider "hostnetwork-v2": Forbidden: not usable by user or serviceaccount, provider "hostnetwork": Forbidden: not usable by user or serviceaccount, provider "hostaccess": Forbidden: not usable by user or serviceaccount, provider "node-exporter": Forbidden: not usable by user or serviceaccount, provider "privileged": Forbidden: not usable by user or serviceaccount]

Impact

RabbitMQ pod will not come up properly.

Conditions

RabbitMQ is installed on a non-default namespace

Workaround

Before installing rabbitMQ on a non-default namespace, provide privileges to "default" service account in the RabbitMQ namespace by running the following command : ? oc adm policy add-scc-to-user privileged -n <RabbitMQ-Namespace> -z <serviceaccount>

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips