Created attachment 1788732 [details]
The console frontend keeps trying to get the ConsoleLink acm-link. When it doesn't exist, it will 404. Console should stop polling.
We should fix this in 4.8 since it creates a lot of noise in the logs. We've had similar issues around ClusterVersion in the past, which generated a number of bug reports.
Search in browser console tab, following request is not found
Failed to load resource: the server responded with a status of 404 (Not Found) https://<console_route>/api/kubernetes/apis/console.openshift.io/v1/consolelinks/acm-console-link
Now we watch for consolelinks
websocket open: /api/kubernetes/apis/console.openshift.io/v1/consolelinks?watch=true&resourceVersion=279066
when acm-console-link is added, we watch acm-console-link
websocket open: /api/kubernetes/apis/console.openshift.io/v1/consolelinks?watch=true&fieldSelector=metadata.name%3Dacm-console-link
In this way, there is no large number of `404 Not Found` errors and still function the same, verified on 4.8.0-0.nightly-2021-06-09-000526
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.