Bug 1903580

Summary: content for a page with invalid namespace in URL keeps on loading
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Karel Srot <ksrot>
Component: GRC & PolicyAssignee: Yu Cao <ycao56>
Status: CLOSED ERRATA QA Contact: Derek Ho <dho>
Severity: low Docs Contact: Mikela Dockery <mdockery>
Priority: unspecified    
Version: rhacm-2.1CC: dhaiduce, gghezzo
Target Milestone: ---Flags: gghezzo: rhacm-2.1.z+
gghezzo: rhacm-2.2+
Target Release: rhacm-2.1.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhacm-2.1.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-17 18:19:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Karel Srot 2020-12-02 12:30:50 UTC 
Description of problem:

So I have this valid namespace 
/multicloud/policies/policy/local-cluster/default.ksrot-policy-grc
where the last part is the name of my policy.

I was just curious whether I could get additional detail by replacing 'local-cluster' with 'all', i.e. the namespace was
/multicloud/policies/policy/alll/default.ksrot-policy-grc

With that the page content keeps loading (indefinitely?).
I shoud be probably forwarded to a different page instead.

Version-Release number of selected component (if applicable):
RHACM 2.2.0

How reproducible:
Always

Steps to Reproduce:
See above
Comment 1 Dale H 2020-12-07 21:18:49 UTC 
Hello, Karel!

Thank you for submitting this bug! I'm currently looking into this issue. Our current logic loads pages based on the namespace and policy name in the URL path. So in this case there's no policy "default.ksrot-policy-grc" in the "all" namespace, so we'll update the behavior to load a "No Resource" page in this case.

Thanks,
Dale
Comment 7 errata-xmlrpc 2021-02-17 18:19:07 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: Red Hat Advanced Cluster Management 2.1.3 security and bug fix 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-2021:0607