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

Unable to override idle timeout for a particular user #8951

Closed
sleshchenko opened this issue Feb 28, 2018 · 0 comments
Closed

Unable to override idle timeout for a particular user #8951

sleshchenko opened this issue Feb 28, 2018 · 0 comments
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template.

Comments

@sleshchenko
Copy link
Member

sleshchenko commented Feb 28, 2018

Description

Unable to override idle timeout for a particular user.

It happens because of lack special implementation of WorspaceActivityManager in multiuser Che, like Codenvy has HostedWorkspaceActivityManager.

Also there are two properties for configuring the ilde timeout:

It is confused which one should be configured. Actually, CHE_WORKSPACE_AGENT_DEV_INACTIVE__STOP__TIMEOUT__MS is deprecated and should be removed at all. Maybe we should add the corresponding alias. Then CHE_LIMITS_WORKSPACE_IDLE_TIMEOUT will be used as the only one property for configuration idle timeout:

  • for all workspaces in case of single user Che;
  • default the idle timeout per user which can be overridden with Resources API.

Reproduction Steps

  1. Login as admin.
  2. Set the idle timeout to 24h for User A.
  3. Login as User A.
  4. Start workspace and close browser tab.
  5. Reopen workspace after 2h.
    Expected: Workspace is active because the idle timeout is overridden for the particular user.
    Actual: Workspace is stopped after 1h because it is default timeout that is configured with che.workspace.agent.dev.inactive_stop_timeout_ms.
@sleshchenko sleshchenko added kind/bug Outline of a bug - must adhere to the bug report template. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. team/platform labels Feb 28, 2018
@mkuznyetsov mkuznyetsov self-assigned this Apr 2, 2018
@mkuznyetsov mkuznyetsov removed the status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. label Apr 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

No branches or pull requests

3 participants