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 #12680

Open
torchiaf opened this issue Nov 26, 2024 · 3 comments · Fixed by #12717
Assignees
Labels
area/dashboard JIRA kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/2 Size Estimate 2 status/backport-candidate
Milestone

Comments

@torchiaf
Copy link
Member

torchiaf commented Nov 26, 2024

Jira issue: SURE-9187, reopened
Related issue #12259

Describe the bug

The users still have the bug reported in #12259

Additional logs from customers:

The API response (no permissions)

Example 1:
{

    "type": "error",

    "links": {},

    "code": "Forbidden",

    "message": "apps.catalog.cattle.io \"rancher-monitoring\" is forbidden: User \"user\" cannot get resource \"apps\" in API group \"catalog.cattle.io\" in the namespace \"cattle-monitoring-system\"",

    "status": 403
}

Example 2:
{

    "type": "error",

    "links": {},

    "code": "Forbidden",

    "message": "statefulsets.apps \"fleet-agent\" is forbidden: User \"user\" cannot get resource \"statefulsets\" in API group \"apps\" in the namespace \"cattle-fleet-system\"",

    "status": 403
}

Proposed Solution

The health boxes should be hidden if the user has no access to the cattle-cluster-agent and fleet-agent objects.

@torchiaf torchiaf added this to the v2.10.1 milestone Nov 26, 2024
@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 Nov 26, 2024
@gaktive gaktive added the JIRA label Nov 26, 2024
@gaktive gaktive modified the milestones: v2.10.1, v2.11.0 Nov 26, 2024
@gaktive
Copy link
Member

gaktive commented Nov 26, 2024

/backport v2.10.1

@aalves08
Copy link
Member

UPDATE

Reproducible with the following conditions in a downstream cluster:

  • Create a standard user
  • Assign them to System project with the custom role View Monitoring

@yonasberhe23
Copy link
Contributor

testing is blocked by #12828

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard JIRA kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/2 Size Estimate 2 status/backport-candidate
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants