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

ResourceTabs and Events table crash if user has no permissions for event schema #13477

Open
torchiaf opened this issue Feb 21, 2025 · 0 comments · Fixed by #13478
Open

ResourceTabs and Events table crash if user has no permissions for event schema #13477

torchiaf opened this issue Feb 21, 2025 · 0 comments · Fixed by #13478
Assignees
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this status/release-blocker
Milestone

Comments

@torchiaf
Copy link
Member

Setup

  • Rancher version: head-d669a7cc2a
  • Rancher UI Extensions:
  • Browser type & version:

Describe the bug

headerFromSchemaColString function throws undefined error if schema input field is null - for instance if a user has no permissions to fetch the event schema.
The function is used to build Events table headers;

We need to add null checks for event schema.

To Reproduce

  • Log in as admin user
  • Create a standard user
  • Follow this guide to create a new project1 Workspace in Fleet as admin, and share it with the standard user: https://fleet.rancher.io/multi-user#isolated-workspaces-in-rancher
  • As admin, create 1 or more GitRepos in project1 .
  • Login as standard user
  • Go to Fleet -> GitRepo -> select a GitRepo and go to details page

Result

The ResourceTab component crashes because the eventSchema is null:

Image

@torchiaf torchiaf added this to the v2.11.0 milestone Feb 21, 2025
@torchiaf torchiaf self-assigned this Feb 21, 2025
@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 Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this status/release-blocker
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant