Hide Forgot
Created attachment 1621500 [details] 404 not found screenshot Description of problem: In the UI, there is 404:Not Found instead of a list of cnv operands. Version-Release number of selected component (if applicable): checked for both alpha bundle 88 in brew, and 2.1.0 bundle 89 from stage How reproducible: always Steps to Reproduce: 1. Install CNV 2. in UI: Installed Operators -> click CNV Operator -> All Instances tab. There is 404:Not Found. Actual results: Screen attached. Expected results: The list of operands like in the attachment to BZ #1716329
moving out to 2.2.
From debugging this together with the UI team (Yaacov Zamir), it looks like the source of the issue is that the UI sends namespace specific requests for global resources, which no longer works. The bug should be probably moved to the UI team, since there is nothing we can do about this on the HCO side. I.e. the requests are sent for /api/kubernetes/apis/cdi.kubevirt.io/v1alpha1/namespaces/default/cdis?limit=250 instead of /api/kubernetes/apis/cdi.kubevirt.io/v1alpha1/cdis?limit=250 It seems that the oc tool caches the resource definitions, so it knows if the resource type is actually a namespaced or not, and sends a properly formatted request - including the namespace only for namespaced resources and ignoring it for global ones. That logic however is no longer implemented at the API level, and the system considers it a wrong request, thus the issue that we see.
Tomas, can you take this?
actually it is an issue in the OLM UI, moving to the correct component.
Payload: 4.3.0-0.nightly-2019-11-21-122827 Checked on OCP 4.3 with above version: Installed Operators -> click CNV Operator -> All Instances tab, there is no "404:not found", but show "No Operands Found " which is correct. The bug is fixed, so move it to Verified.
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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062