Description of problem: There are unnecessary console.error logs for resources which were not found (404). Even though, they are expected not to be found (for example with optional FirehoseResource property). How reproducible: 100 Steps to Reproduce: Please see https://bugzilla.redhat.com/show_bug.cgi?id=1821259, which is fixed by a hack (fetching the whole list). Expected results: It is possible to fetch standalone resource and specify suppression of 404 errors
This is working as intended. The console messages are harmless and not displayed to the user. These are only for developers. It would be worse not to log the 404 response.
The calling code should handle the failed promise if it's not.
In our case that is not possible, because we are using Firehose which calls watchK8sObject (k8sGet), which does not have any option of handling this. This feature could be then added to firehose, if we don't want to modify the co-fetch.
Sorry, I disagree with the premise. The 404 network requests are accurate and helpful for debugging. They aren't displayed to the user. We shouldn't misuse the k8s fieldSelector to suppress the message.
In general, I agree that it is helpful to have such logs. Nevertheless, VMI case is special, because we expect that it might not be there - VM page behaves differently according to that. This feature would just help to cleanup the log a bit.