Description of problem (please be detailed as possible and provide log
snippests):
After upgrade to 4.12 the OSDs will not start, and fail with the following event:

1s          Warning   FailedCreate        replicaset/rook-ceph-osd-0-7c79476d5d                Error creating: pods "rook-ceph-osd-0-7c79476d5d-" is forbidden: unable to validate against any security context constraint: [provider "anyuid": Forbidden: not usable by user or serviceaccount, provider restricted-v2: .spec.securityContext.hostPID: Invalid value: true: Host PID is not allowed to be used, spec.volumes[2]: Invalid value: "hostPath": hostPath volumes are not allowed to be used, spec.volumes[3]: Invalid value: "hostPath": hostPath volumes are not allowed to be used, spec.volumes[5]: Invalid value: "hostPath": hostPath volumes are not allowed to be used, spec.volumes[6]: Invalid value: "hostPath": hostPath volumes are not allowed to be used, provider restricted-v2: .initContainers[0].privileged: Invalid value: true: Privileged containers are not allowed, provider restricted-v2: .initContainers[0].hostPID: Invalid value: true: Host PID is not allowed to be used, provider restricted-v2: .initContainers[1].privileged: Invalid value: true: Privileged containers are not allowed, provider restricted-v2: .initContainers[1].hostPID: Invalid value: true: Host PID is not allowed to be used, provider restricted-v2: .initContainers[2].privileged: Invalid value: true: Privileged containers are not allowed, provider restricted-v2: .initContainers[2].hostPID: Invalid value: true: Host PID is not allowed to be used, provider restricted-v2: .initContainers[3].runAsUser: Invalid value: 0: must be in the ranges: [1000630000, 1000639999], provider restricted-v2: .initContainers[3].privileged: Invalid value: true: Privileged containers are not allowed, provider restricted-v2: .initContainers[3].hostPID: Invalid value: true: Host PID is not allowed to be used, provider restricted-v2: .containers[0].runAsUser: Invalid value: 0: must be in the ranges: [1000630000, 1000639999], provider restricted-v2: .containers[0].privileged: Invalid value: true: Privileged containers are not allowed, provider restricted-v2: .containers[0].hostPID: Invalid value: true: Host PID is not allowed to be used, provider restricted-v2: .containers[1].privileged: Invalid value: true: Privileged containers are not allowed, provider restricted-v2: .containers[1].hostPID: Invalid value: true: Host PID is not allowed to be used, provider restricted: .spec.securityContext.hostPID: Invalid value: true: Host PID is not allowed to be used, provider restricted: .initContainers[0].privileged: Invalid value: true: Privileged containers are not allowed, provider restricted: .initContainers[0].hostPID: Invalid value: true: Host PID is not allowed to be used, provider restricted: .initContainers[1].privileged: Invalid value: true: Privileged containers are not allowed, provider restricted: .initContainers[1].hostPID: Invalid value: true: Host PID is not allowed to be used, provider restricted: .initContainers[2].privileged: Invalid value: true: Privileged containers are not allowed, provider restricted: .initContainers[2].hostPID: Invalid value: true: Host PID is not allowed to be used, provider restricted: .initContainers[3].runAsUser: Invalid value: 0: must be in the ranges: [1000630000, 1000639999], provider restricted: .initContainers[3].privileged: Invalid value: true: Privileged containers are not allowed, provider restricted: .initContainers[3].hostPID: Invalid value: true: Host PID is not allowed to be used, provider restricted: .containers[0].runAsUser: Invalid value: 0: must be in the ranges: [1000630000, 1000639999], provider restricted: .containers[0].privileged: Invalid value: true: Privileged containers are not allowed, provider restricted: .containers[0].hostPID: Invalid value: true: Host PID is not allowed to be used, provider restricted: .containers[1].privileged: Invalid value: true: Privileged containers are not allowed, provider restricted: .containers[1].hostPID: Invalid value: true: Host PID is not allowed to be used, provider "nonroot-v2": Forbidden: not usable by user or serviceaccount, provider "nonroot": Forbidden: not usable by user or serviceaccount, provider "noobaa": Forbidden: not usable by user or serviceaccount, provider "noobaa-endpoint": 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 "ocs-metrics-exporter": Forbidden: not usable by user or serviceaccount, provider rook-ceph: .spec.securityContext.hostPID: Invalid value: true: Host PID is not allowed to be used, provider rook-ceph: .initContainers[0].hostPID: Invalid value: true: Host PID is not allowed to be used, provider rook-ceph: .initContainers[1].hostPID: Invalid value: true: Host PID is not allowed to be used, provider rook-ceph: .initContainers[2].hostPID: Invalid value: true: Host PID is not allowed to be used, provider rook-ceph: .initContainers[3].hostPID: Invalid value: true: Host PID is not allowed to be used, provider rook-ceph: .containers[0].hostPID: Invalid value: true: Host PID is not allowed to be used, provider rook-ceph: .containers[1].hostPID: Invalid value: true: Host PID is not allowed to be used, provider "node-exporter": Forbidden: not usable by user or serviceaccount, provider "rook-ceph-csi": Forbidden: not usable by user or serviceaccount, provider "privileged": Forbidden: not usable by user or serviceaccount]


Version of all relevant components (if applicable):
4.12.5

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, the storage is not accessible right now as all OSDs are down.

Is there any workaround available to the best of your knowledge?
No work-around

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
4 

Can this issue reproducible?
Yes, at customer site

Can this issue reproduce from the UI?
N/A

If this is a regression, please provide more details to justify this:
N/A


Additional info: