Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rancher UI New component health checks "Cattle" and "Fleet" fail for standard users with only project membership #12259

Open
aalves08 opened this issue Oct 15, 2024 · 1 comment
Assignees
Labels
JIRA kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/3 Size Estimate 3 status/backport-candidate
Milestone

Comments

@aalves08
Copy link
Member

aalves08 commented Oct 15, 2024

SURE-9187

Setup

  • Rancher version: 2.9.2

Describe the bug
One of our users reported that in Rancher 2.9.2 in the UI Cluster status/Cluster Dashboard, it appears that some new component health checks were introduced on the cluster landing page in the GUI.

These checks work fine if you are logged in with sufficient access. However, if you are logged in as a standard project member user, it looks like you don't have access to the relevant data that feeds these checks. As a result it looks like they are failing which is a cause for concern for normal Rancher users who don't need to be aware of the state of the Cattle agents or Fleet agents running on the cluster.

image-2024-10-11-17-52-15-372

To Reproduce

  • Crete a "userA" as Standard user, all default no changes
  • Create a new project under the local cluster called "new-proj"
  • Create a new namespace under the "new-proj" project, called "new-namespace"
  • Add "userA" as project Member to the "new-proj" project in the local cluster
  • Login as "userA" in Rancher and go to the local cluster cluster explorer
  • The boxes for cattle and fleet appear in red and cannot get the status correctly

Actual behavior:
The project member can see a health check that looks like a component is failing

Expected behavior:
The project member should not see the health checks failing if it doesn't concern them.

@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Oct 15, 2024
@gaktive gaktive added this to the v2.10.0 milestone Oct 15, 2024
@gaktive gaktive added the size/3 Size Estimate 3 label Oct 16, 2024
@mantis-toboggan-md
Copy link
Member

potential solution from discussion elsewhere:

we would probably need to check if they can see the specific namespace (i think it's different for local/not local) of the required resource

@mantis-toboggan-md mantis-toboggan-md self-assigned this Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
JIRA kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/3 Size Estimate 3 status/backport-candidate
Projects
None yet
Development

No branches or pull requests

3 participants