Description of problem (please be detailed as possible and provide log
snippests): Customer has noticed 404 errors in the audit logs of their kube-api servers. The resources being called no longer exist, as they are relics of older versions of OCS/ODF.

PVC named db-noobaa-core-0

Services named

noobaa-db

ocs-provider-server

Secrets named

noobaa-root-master-key

ocs-provider-server

Deployments named ocs-provider-server

Example of 404 errors:
-----------
$ jq 'select((.responseStatus.code == 404) and (.objectRef.namespace == "openshift-storage") and (.objectRef.resource != "ephemeralreports")) | "(.user.username) and got response (.responseStatus.message)"' audit-results.json | sort | uniq -c | sort -hr
6128 "system:serviceaccount:openshift-storage:noobaa and got response persistentvolumeclaims \"db-noobaa-core-0\" not found"
3064 "system:serviceaccount:openshift-storage:noobaa and got response services \"noobaa-db\" not found"
3064 "system:serviceaccount:openshift-storage:noobaa and got response secrets \"noobaa-root-master-key\" not found"
398 "system:serviceaccount:openshift-storage:ocs-operator and got response services \"ocs-provider-server\" not found"
398 "system:serviceaccount:openshift-storage:ocs-operator and got response secrets \"ocs-provider-server\" not found"
398 "system:serviceaccount:openshift-storage:ocs-operator and got response deployments.apps \"ocs-provider-server\" not found"
----------------------

Must gather can be found at: 03931006/0080-must-gather-latest.tar.gz/

Sos report can be found at: 03931006/0060-sosreport-l17nocp01-f2l2r-master-0-03931006-2024-09-16-zstchpo.tar.xz

Ceph info can be found at: 03931006/0030-odf-logs.tar.gz

Version of all relevant components (if applicable):
OCP 4.15.21
ODF 4.15.6

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No

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