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

[forwardport v2.9.0] Disabled In time is displaying for a user which is already in Disabled state #11073

Closed
github-actions bot opened this issue May 21, 2024 · 0 comments · Fixed by #11262
Assignees
Labels
QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None
Milestone

Comments

@github-actions
Copy link
Contributor

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

Original issue body:

Rancher Server Setup

  • Rancher version: v2.8.s4-318b423a3124919eb59fe0f4af024f2699645ffd-head
  • Installation option (Docker install/Helm Chart): HA
    • If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):
  • Proxy/Cert Details:

User Information

  • What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)
    Admin

Describe the bug
Disabled In column displaying the value for a user who is already in Disabled/Inactive state

STEPS To Reproduce

  1. Provision rancher HA
  2. Create a user test1
  3. Login as user test1 and logout
  4. Login as admin and Update settings 'disable-inactive-user-after' to 5 mins
    kubectl edit setting disable-inactive-user-after
  5. Check for the Disabled In time before and after 5mins (Rancher->users)

Result

  1. The user is Inactive after 5mins, after 5mins the time keep getting increased and it is showing the time till it got deleted.

Expected Result

  1. Once the user is Inactivated, the date on that user should be blank, it should not continue to display the time after it got disabled

Screenshots
image

Additional context

@github-actions github-actions bot added QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None labels May 21, 2024
@github-actions github-actions bot added this to the v2.9.0 milestone May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant