Description of problem:
User does not have any project, login and check Status page, there is "No Resources Found" in the hidden section.
Version-Release number of selected component (if applicable):
registry.reg-aws.openshift.com:443/openshift/ose-console v4.0 77d6a7fb5cb9
Steps to Reproduce:
1. Make sure user does not have any project, login and check Status page.
1. There is "No Resources Found" in the hidden section.
1. The "No Resources Found" should be removed under current project which is "default"
Jon, is it easy to show something else when showing the "fake" message?
It would be pretty easy to replace this with a custom message or react component. We would just need to figure out what would go in its place.
Created attachment 1520676 [details]
the wrong display as no resource found
On Status page it still displays "No Resources Found" and url is overview/ns/default, please refer to the screenshot(attachment), thanks!
Tested on the version:
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.0.0-0.nightly-2019-01-15-010905 True False 11m Cluster version is 4.0.0-0.nightly-2019-01-15-010905
This is expected for system namespaces like default. We don't show the empty state message with add-to-project buttons because we don't want to encourage users to add content to system namespaces. See
I'm not sure what else we should show here. We could display a 403 forbidden error, but that seems less friendly. Here the content uses a disabled style to indicate that it's not active/real, and there's a clear call-to-action at the top of the page. You probably only get here by ignoring the message to create a project when first logging in.
> Expected results:
> 1. The "No Resources Found" should be removed under current project which is "default"
I think it would look more broken if we leave the entire area below Project Status blank.
There's a fine line between not found and forbidden. If you have an account with limited permissions, you might not know if a resource doesn't exist or if you simply don't have permission to view.
For the reasons above, I think this is a design choice and not a bug. The UI is working as intended.