Skip to content

[backport v2.11.14] Refreshing the project membership page assigns wrong role to a member #17566

@rancher-ui-project-bot

Description

@rancher-ui-project-bot

This is a backport issue for #13992, automatically created via GitHub Actions workflow initiated by @rak-phillip

Original issue body:

SURE-10030
SURE-11574

Setup

  • Rancher version: SUSE Rancher 2.10.1, SUSE Rancher 2.10.3, SUSE Rancher 2.11.0, head
  • Rancher UI Extensions: NA
  • Browser type & version: Latest Firefox & Chrome

Describe the bug

Refreshing the Project membership page, duplicates members in such a way that it appears to roles have be incorrectly assigned.

To Reproduce

  • Create 3 users test,test2, test3, and test project.
  • Navigate to the "Clusters and Project Members" page and click on " Project Membership" (eg: https://localhost/dashboard/c/local/explorer/members#project-membership)
  • Add the above users as project members with project permission like --> test-Project Owner, test2-Project Member, test3-Readonly. to the 'test' project.
  • Refresh the page

Result

After the Page Refresh, The member role gets a different value. i.e. test2 member is getting "Readonly" permission and the 'test3' member gets Project Member permission.

Expected Result

Page Refresh should show the right values in the UI (ProjectMembership)

Screenshots

Image

Additional context

You can work around this issue by sorting by state on this page.

This could be an issue with sorting, more information is needed to pinpoint the root cause of this behavior.

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions