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
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
GitOpsService Operand page shows a 404:Not Found error
GitOpsService Operand page should display the list of GitOpsService operands
PR to fix this bug: https://github.com/openshift/console/pull/8379
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.
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
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.
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.
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.