Bug 2111437 - 404: Not Found on OCP UI in CR view
Summary: 404: Not Found on OCP UI in CR view
Keywords:
Status: CLOSED DUPLICATE of bug 2109709
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.11
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Robb Hamilton
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-27 10:18 UTC by Lukasz Gebarowski
Modified: 2022-11-08 14:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 14:38:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
OCP UI view (100.67 KB, image/png)
2022-07-27 10:18 UTC, Lukasz Gebarowski
no flags Details
ocp ui (52.03 KB, image/png)
2022-07-27 10:19 UTC, Lukasz Gebarowski
no flags Details

Description Lukasz Gebarowski 2022-07-27 10:18:55 UTC
Created attachment 1899615 [details]
OCP UI view

Description of problem:

Comparison of request between OCP 4.10 and 4.11:

4.10 (HTTP code 200)
GET https://console-openshift-console.apps.release-ltsr.8hwx.p1.openshiftapps.com/api/kubernetes/apis/operator.ibm.com/v1alpha1/ibmlicensings?limit=250&cluster=local-cluster

4.11 (HTTP code 404)
GET https://console-openshift-console.apps.licensing-x.cp.fyre.ibm.com/api/kubernetes/apis/operator.ibm.com/v1alpha1/namespaces/ibm-common-services/ibmlicensings?limit=250&cluster=local-cluster

Version-Release number of selected component (if applicable):
4.11.0-rc.5

Comment 1 Lukasz Gebarowski 2022-07-27 10:19:27 UTC
Created attachment 1899616 [details]
ocp ui

Comment 2 Robb Hamilton 2022-11-08 14:38:43 UTC
Given this was reported in 4.11.0-rc.5, it seems to be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2109709 (the PR for which merged the same day this bug was reported).  If this is still a problem, please reopen.

*** This bug has been marked as a duplicate of bug 2109709 ***


Note You need to log in before you can comment on or make changes to this bug.