-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.16
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Customer is seeting 404 api calls to a logging config map in the openshift-vsphere-infra namespace. However, this is a newly installed cluster and this config map has never existed.
Version-Release number of selected component (if applicable):
4.16
How reproducible:
seen on newly created cluster installed on vmware
Steps to Reproduce:
1. install ocp 4.16 using ipi method on vmware 2. look through audit logs for failures for the nodes 3.
Actual results:
kubectl-dev_tool audit -f kube-apiserver --by verb --user=system:node:prod1 --failed-only -otop had 63804 line read failures count: 24100, first: 2025-07-30T20:02:14-04:00, last: 2025-07-31T14:22:34-04:00, duration: 18h20m19.978828s Top 10 "GET" (of 24080 total hits): 24080x [107.690483ms] [404-24075,500-4] /api/v1/namespaces/openshift-vsphere-infra/configmaps/logging?timeout=30s [system:node:prod1]
Expected results:
no 404 errors
Additional info: