pipe-cd / pipe-cd/pipecd

Upgrading Piped in UI or manually

Open
#4,497 9 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What happened:

I've installed PipeCD at version v0.43.1, then I deploy with helm upgrade with the same version Piped, then I want to try upgrade to latest release, for example it fails, but it still tries to upgrade to latest, it is still checking the latest releases /ListLatestReleases, it does not indicate UI if it can upgrade or not, it just says Upgrading to..., I wanted to upgrade to v0.44.0, so I tried it manually with helm upgrade, when I am on the version I've selected in the UI, the message Upgrading to ... dissapears, but when I am downgrading to 0.43.1 back, it starts to again in UI show the same message, Upgrading to v0.44.0, when I deleted the Piped and then installed with the helm upgrade the actual latest release version v0.44.2 then I refreshed on the UI page, it says Upgrading to v0.44.0, user should stop the PipeCD, to stop automatically triggering upgrading, if it fails or if the user tries to upgrade it with remote config via helm upgrade

Environment:

  • piped version: v0.43.1
  • control-plane version: v0.43.1

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.

Research direction

Start by tracing the UI's upgrade status and the /ListLatestReleases entry point while reproducing the Helm upgrade and downgrade scenarios described. Done means failed or manually completed upgrades no longer leave a stale “Upgrading to” message, and automatic upgrade attempts can be stopped as requested.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.