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

[ws-manager] do not overwrite failed state #11419

Merged
merged 1 commit into from
Jul 15, 2022
Merged

[ws-manager] do not overwrite failed state #11419

merged 1 commit into from
Jul 15, 2022

Conversation

sagor999
Copy link
Contributor

Description

Do not clear up any failed state, as that will trip server in thinking that workspace has not failed, when in reality it did.
Which in turn causes subsequent workspace start to fail as server will instruct to restore workspace from backup.

Related Issue(s)

Fixes #10315

How to test

Release Notes

none

Documentation

Werft options:

  • /werft with-preview

@sagor999 sagor999 requested a review from a team July 15, 2022 18:57
@github-actions github-actions bot added the team: workspace Issue belongs to the Workspace team label Jul 15, 2022
@sagor999
Copy link
Contributor Author

/hold
to fix fixtures test

@sagor999
Copy link
Contributor Author

/unhold

@roboquat roboquat merged commit 96c136f into main Jul 15, 2022
@roboquat roboquat deleted the pavel/10315 branch July 15, 2022 19:36
@roboquat roboquat added deployed: workspace Workspace team change is running in production deployed Change is completely running in production labels Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployed: workspace Workspace team change is running in production deployed Change is completely running in production release-note-none size/S team: workspace Issue belongs to the Workspace team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[ws-manager] workspaces failed to start
3 participants