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

Upgrade to 1.4 failed #1082

Open
atchadwick opened this issue Feb 5, 2025 · 1 comment
Open

Upgrade to 1.4 failed #1082

atchadwick opened this issue Feb 5, 2025 · 1 comment
Assignees

Comments

@atchadwick
Copy link

Upgraded to 1.4 however got a failed error (which i have lost) but I think it was complaining because I patched the service to LB.

However Everest thinks its on 1.4 but when i try to add a new namespace to monitor etc I get this error:

everestctl namespaces add  tenant3 --operator.mongodb=true --operator.postgresql=true --take-ownership
× Installing namespace 'tenant3'
        another operation (install/upgrade/rollback) is in progress
2025-02-05T10:58:54Z    error   output/command.go:64    another operation (install/upgrade/rollback) is in progress
× another operation (install/upgrade/rollback) is in progress
everestctl upgrade

 🚀 You're running the latest version of Everest
helm list -A
NAME                    NAMESPACE               REVISION        UPDATED                                 STATUS          CHART                           APP VERSION
everest-system          everest-system          4               2025-01-31 15:11:32.369282461 +0000 UTC deployed        everest-1.4.0                   1.4.0

Is there anything I can do to resolve this please

@mayankshah1607
Copy link
Member

Hi @atchadwick , thanks for reporting this.

I tried to reproduce this failure by patching the service type prior to the upgrade, but the upgrade still worked fine, without any issues. I'm suspecting there's something else. It would have been super useful to know the exact error message to pinpoint the issue, but I think we can still try to reset the state of the upgrade by following these steps:

  1. Delete all secrets of type helm.sh/release.v1 in namespace everest-system and DB namespaces
NAME                                   TYPE                 DATA   AGE
everest-accounts                       Opaque               1      13m
everest-jwt                            Opaque               2      13m
sh.helm.release.v1.everest-system.v1   helm.sh/release.v1   1      8m23s  <--- [Delete this one]
  1. Revert the image of the everest-server deployment
kubectl set image deployment/everest-server -n everest-system everest=percona/everest:1.3.0
  1. Upgrade to 1.4.0 (using CLI 1.4.0)
./everestctl-1.4.0 upgrade

Please let me know it this resolves your issue. 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants