Keeps the crashed workload in the deployment if zos decides to delete it

Open
#2,350 0 comments 0 reactions 1 assignee View on GitHub

@rawdaGastan is already working on this.

Since Aug 6, 2024.

Assessment

This issue has not been assessed yet.

Description

type_feature

Is your feature request related to a problem? Please describe

in this issue https://github.com/threefoldtech/zos/issues/2349 as the VM crashed many times, zos deleted this zmachine workload. And when the user called zos.deployment.get, the workload disappeared.

Describe the solution you'd like

as a suggestion besides using zos.deployment.changes, if zos decides to delete or stop this workload, we might keep this workload in the deployment with a state error, so the user can see that he has a failing workload. Otherwise, he most probably forgets that he has this workload.

Dominant language
Go
Stars
95
Forks
22
Avg merge
2m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from threefoldtech/zos

All issues in threefoldtech/zos

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.