Description of problem: When the user exports an application with the Primer GitOps page the topology shows a Deployment with a surrounding Export CSV "Primer". When the user clicks on that CSV it was opened in the sidebar. When the user now clicks on the title "(E) primer" to open the detail page of that resource, the user was redirected to a page which shows a skeleton loading indicator 'forever'. Version-Release number of selected component (if applicable): 4.9 How reproducible: Always Steps to Reproduce: 1. Open Operator Hub and install the "Primer" GitOps Operator 2. Switch to developer perspective 3. Import at least one Application to enable the Export button in topology 4. If not opened yet, open the topology, and click the "Export Application" button 5. Wait until the export finishs and a new Deployment "primer-export-primer" was shown 6. Click on the Export "primer" and then click on the linked "(E) primer" title in the sidebar Actual results: 1. User is redirected to a page which never finishs the loading. Linked page looks like this: /k8s/ns/christoph/operators.coreos.com~v1alpha1~ClusterServiceVersion/gitops-primer.v0.0.1/primer.gitops.io~v1alpha1~Export/primer 2. When open the Deployment "primer-export-primer" detail page by clicking it in the sidebar (/k8s/ns/christoph/deployments/primer-export-primer/yaml) the managed by (E) "primer" link links also to this invalid URL. Expected results: 0. The page which could not fetch the right data should show a eror message instead of loading forever. 1.+2. User should be redirected to a page which shows the generic resource detail page Open the Export detail page over the search works fine and opens this page: /k8s/ns/christoph/exports/primer Additional info:
@dsantra This issue doesn't seem to be fixed as I still see the details page loading forever. Verified on - 4.10.0-0.nightly-2021-12-14-083101.
@divgupta checked it on 4.10.0-0.ci-2021-12-16-184808 , I am not able to reproduce the issue anymore
Could verify this as well on 4.10.0-0.nightly-2021-12-16-185411.
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.10.3 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. https://access.redhat.com/errata/RHSA-2022:0056