Bug 1937929 - Operand page shows a 404:Not Found error for OpenShift GitOps Operator
Summary: Operand page shows a 404:Not Found error for OpenShift GitOps Operator
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Chetan
QA Contact: Gajanan More
Depends On:
Blocks: 1942160
TreeView+ depends on / blocked
Reported: 2021-03-11 18:21 UTC by Chetan
Modified: 2021-07-27 22:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-07-27 22:52:37 UTC
Target Upstream Version:

Attachments (Terms of Use)
Screenshot of the 404 error in the GItOpsService operand page (89.06 KB, image/png)
2021-03-11 18:21 UTC, Chetan
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:53:08 UTC

Description Chetan 2021-03-11 18:21:13 UTC
Created attachment 1762731 [details]
Screenshot of the 404 error in the GItOpsService operand page

Description of problem:
On installation of OpenShift GitOps operator, the Operator UI shows a 404: Not Found error in the GitOpsService operand page

Version-Release number of selected component (if applicable): OCP 4.7

How reproducible:

Steps to Reproduce:
1. Install OpenShift GitOps Operator from Operator Hub
2. Navigate to installed operators > GitOps Operator > GitOpsServices operand tab
3. Observe the 404: Not Found error

Actual results:

GitOpsService Operand page shows a 404:Not Found error

Expected results:

GitOpsService Operand page should display the list of GitOpsService operands

Comment 1 Chetan 2021-03-15 12:34:08 UTC
PR to fix this bug: https://github.com/openshift/console/pull/8379

Comment 2 Christoph Jerolimov 2021-03-23 10:08:24 UTC
Verified on 4.8.0-0.nightly-2021-03-22-064955

Could verify that also that it also/still exist on 4.7.3

@cbanavik should we backport this small fix? It's only low severity.

Comment 3 Chetan 2021-03-23 15:51:20 UTC

Comment 4 Chetan 2021-03-23 16:02:49 UTC
Hi @cjerolim,  , 

Thanks for verifying this. It would be better if we can get it backported to 4.7 since OpenShift GitOps will be going GA with 4.7

Comment 5 Christoph Jerolimov 2021-03-23 18:58:04 UTC
Hi @cbanavik, ack. I created a cherry-pick for this, this will be tracked in the BZ issue https://bugzilla.redhat.com/show_bug.cgi?id=1942160 and in PR https://github.com/openshift/console/pull/8450.

Comment 6 Christoph Jerolimov 2021-04-14 17:00:41 UTC
Hi @cbanavik, based on See also https://github.com/openshift/console/pull/8450#issuecomment-819563929 this fix was it was not picked for merging for the upcoming 4.7 release. This status is also tracked in the 4.7 BZ issue https://bugzilla.redhat.com/show_bug.cgi?id=1942160.

This prio is based on the severity which we set to low here (and in 1942160). If this is an issue you can ask the release team in #forum-release, or increase the severity of the backport for the next time. I think this will get merged in the next z-stream anyway.

Comment 9 errata-xmlrpc 2021-07-27 22:52:37 UTC
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.


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