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.

Sign up for GitHub

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

Jump to bottom

[Bug]: wrong timezone is used when suspending a namespace from "RunningForced" state #27

Closed
eze-kiel opened this issue Oct 11, 2021 · 1 comment
Closed

[Bug]: wrong timezone is used when suspending a namespace from "RunningForced" state #27

eze-kiel opened this issue Oct 11, 2021 · 1 comment
Assignees
@eze-kiel
Labels
bug Something isn't working

Comments

@eze-kiel
Copy link
Member

Current Behavior:

Currently, the lifespan of a namespace in "RunningForced" state is hardcoded (4 hours, see #4). But after having started a namespace in "RunningForced" state for more than 4 hours, it didn't scale down.

Expected Behavior:

Being suspended after 4 hours as planned.

Steps to reproduce

Deploy version v0.7.1 and annotate a namespace as "RunningForced". Note the time and wait for 4 hours
@eze-kiel eze-kiel added the bug Something isn't working label Oct 11, 2021
@eze-kiel eze-kiel self-assigned this Oct 11, 2021
@eze-kiel
Copy link
Member Author

fixed in #28

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eze-kiel eze-kiel

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eze-kiel