Created attachment 1867301 [details] Logout failure Description of the problem: Trying to logout is not working as expected. Please find attached screenshots. Found the behavior on the following snapshot: 2.5.0-DOWNSTREAM-2022-03-17-03-36-41 Infrastructure: aws arm, openstack Release version: 2.5 OCP version: 4.10.3, 4.10.0 Browser Info: Chrome Steps to reproduce: 1. Clear cache/cookies from the browser/open a new window 2. Log into ACM console as an admin (kubeadmin) 3. Logout Actual results: Initially, It fails to logout with 404 and nothing happens. After a couple of mins, the web app continuously refreshes itself. Expected results: Successfully log out. Additional info: At times it logs out when other clusters are open on the browser.
G2Bsync 1076487076 comment mark-nc Wed, 23 Mar 2022 15:25:10 UTC G2Bsync The root cause of this bug has been identified. The ingress for the logout route in the `grc-ui` backend server code was more specific than the ingress rules for `console` so part of the logout code was being run by the `console` frontend and part by the `grc-ui` backend when that was not intended once the console backend code was available. Once `grc-ui` was removed from the 2.5 builds, a bug in the console backend code was exposed for logout. We are working on a fix and should have it ready soon.
G2Bsync 1092115911 comment mark-nc Thu, 07 Apr 2022 19:21:34 UTC G2Bsync The fix is in downstream build 2.5.0-DOWNSTREAM-2022-04-07-07-21-43 which is based on upstream 2.5.0-SNAPSHOT-2022-04-07-07-21-43. I have verified the fix is working on the upstream build.
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 (Important: Red Hat Advanced Cluster Management 2.5 security updates, images, and bug fixes), 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:4956
If the cluster status is showing as "Running" in Red Hat Advanced Cluster Management for Kubernetes, it typically indicates that the cluster is operational and functioning properly. The "Running" status means that the cluster is active and available for use. https://www.ballsportspro.com/can-you-hit-a-pickleball-with-your-hand-read-before-you-play/ If you received a confusing message related to the cluster status, it might be due to a miscommunication or a specific error message you encountered. It would be helpful if you could provide more details about the specific message you received, so I can assist you further in understanding the issue and providing a more accurate response.