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

❌ Failed to upgrade Dapr: release name is invalid: #1117

Closed
isayden opened this issue Oct 20, 2022 · 11 comments · Fixed by #1118
Closed

❌ Failed to upgrade Dapr: release name is invalid: #1117

isayden opened this issue Oct 20, 2022 · 11 comments · Fixed by #1118
Assignees
Labels
area/cli kind/bug Something isn't working P1 size/XS 2 days work triaged/resolved The issue has been triaged
Milestone

Comments

@isayden
Copy link

isayden commented Oct 20, 2022

Expected Behavior

Successfully upgraded version through cli

Actual Behavior

dapr --version

CLI version: 1.9.1
Runtime version: 1.4.3
An error was reported when executing this upgrade command.

#dapr upgrade --runtime-version 1.8.5 -k
ℹ️ Container images will be pulled from Docker Hub
ℹ️ Dapr control plane version 1.6.0 detected in namespace dapr-system
ℹ️ Starting upgrade...
❌ Failed to upgrade Dapr: release name is invalid:

Steps to Reproduce the Problem

Use the following command
#dapr upgrade --runtime-version 1.8.5 -k

@isayden isayden added the kind/bug Something isn't working label Oct 20, 2022
@pravinpushkar
Copy link
Contributor

@isayden Could you please provide more information on the current installation and how you installed it. Did you use self hosted helm charts or modified the release name somewhere?

Your dapr version says 1.4.3 but while upgrading it says version 1.6.0.

@isayden
Copy link
Author

isayden commented Oct 20, 2022

It was installed too long ago. The use
#dapr init -k
I didn't modify the release name somewhere,
dapr-cli 1.9 I just upgraded because I want to upgrade the version of dapr
image

@pravinpushkar
Copy link
Contributor

oh ok, So, control plane is at 1.6.0. I just upgraded a cluster to 1.8.5 from 1.6.0. It ran just fine.

By any chance would you be able to install a fresh cluster and try upgrade.

@yaoyaoio
Copy link
Contributor

because in helm list not found dapr
dapr cli upgrades dapr clusters that already exist in helm

@yaoyaoio yaoyaoio mentioned this issue Oct 20, 2022
3 tasks
@shubham1172
Copy link
Member

@isayden can you please also share the output of helm list -A?

@isayden
Copy link
Author

isayden commented Oct 21, 2022

@shubham1172 sure
image

@yaoyaoio
Copy link
Contributor

yaoyaoio commented Oct 21, 2022

@shubham1172
dapr upgrate calls the helm.NewList() get about releases list.
function using filters dapr with status = deployed and status = failed
if status ! = deployed | failed . return empty releases list
@isayden is my firend
his dapr cluster in helm status = pending_upgrade. so using helm list --all -n dapr-system not using helm list -A or helm list -n dapr-system.

@yaoyaoio
Copy link
Contributor

I thinks dapr status = (deployed | failed) in helm 。To meet the upgrade requirements

@isayden
Copy link
Author

isayden commented Oct 21, 2022

image

@yaoyaoio
Copy link
Contributor

I think the user needs to be alerted

#1118

@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale label Nov 20, 2022
@mukundansundar mukundansundar added P1 area/cli size/XS 2 days work triaged/resolved The issue has been triaged and removed stale labels Nov 20, 2022
@mukundansundar mukundansundar added this to the v1.10 milestone Nov 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cli kind/bug Something isn't working P1 size/XS 2 days work triaged/resolved The issue has been triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants