Skip to content

Disabling autostop causes workspace to get stuck with last autostop value #15390

@code-asher

Description

@code-asher

To reproduce:

  1. Create a new template using the "Docker Containers" starter template (notice it does not allow customizing the autostop and has a default of 24 hours).
  2. Create a workspace using that template. The workspace must be created while autostop is currently enabled. Workspaces that are initially created with autostop disabled somehow do not have any problems updating correctly.
  3. Disable autostop in the template through the UI.
  4. Update the workspace, notice it will continue to say "stops in a day" despite autostop being disabled in the template, and showing as disabled in the workspace settings.
  5. New workspaces are fine and do not have any autostop.

I think the default autostop gets set on the workspace, but when you disable autostop it does not then remove it from the workspaces, and you cannot change it as a user either because autostop is disabled in this scenario.

Metadata

Metadata

Labels

customer-reportedBugs reported by enterprise customers. Only humans may set this.s2Broken use cases or features (with a workaround). Only humans may set this.

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy