pipe-cd / pipe-cd/pipecd

Deployment is stuck at RUNNING state if it unable to rollback in case of failure

Open
#3,468 3 comments 0 reactions 1 assignee View on GitHub

@khanhtc1202 is already working on this.

Since Apr 4, 2022.

area/piped kind/bug
Dominant language
Go
Stars
1.4k
Forks
364
Avg merge
1d 4h
Merged PRs (30d)
84

Description

What happened:

When the deployment of kind k8s got errors (because of kubectl version mismatch - for instance), the ROLLBACK stage will be started. If the ROLLBACK is failed as well, the deployment is stuck at RUNNING state.

What you expected to happen:

In case of k8s failure error, piped should be able to finish the deployment regardless k8s issue.

How to reproduce it:

Environment:

  • piped version: 0.26.0
  • control-plane version: 0.27.1
  • Others:

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.