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

Helm Upgrade #4300

Closed
liamkelly-esure opened this issue Jan 16, 2025 · 1 comment
Closed

Helm Upgrade #4300

liamkelly-esure opened this issue Jan 16, 2025 · 1 comment

Comments

@liamkelly-esure
Copy link

liamkelly-esure commented Jan 16, 2025

Describe the bug
Unable to helm upgrade dynatrace-operator 1.3.2 > 1.4.0

To Reproduce
Steps to reproduce the behavior:

  1. Installed dynatrace-operator
helm install dynatrace-operator --version 1.3.2  oci://public.ecr.aws/dynatrace/dynatrace-operator --create-namespace --namespace dynatrace --atomic

Then created activegate yaml (produced via DT) and applied it.

kc apply -f dynakube.yaml

Then attempted a helm upgrade to version 1.4.0

helm upgrade dynatrace-operator --version 1.4.0  oci://public.ecr.aws/dynatrace/dynatrace-operator  --namespace dynatrace --atomic

Which then produced the following error:

Error: UPGRADE FAILED: an error occurred while rolling back the release. original upgrade error: client rate limiter Wait returned an error: context deadline exceeded: cannot patch "dynakubes.dynatrace.com" with kind CustomResourceDefinition: CustomResourceDefinition.apiextensions.k8s.io "dynakubes.dynatrace.com" is invalid: status.storedVersions[1]: Invalid value: "v1beta3": must appear in spec.versions

Expected behavior
The upgrade to succeed.

Additional context
Deploying the helm chart to a kubernetes cluster. I can remove DT 1.3.2 completely and install 1.4.0 without any issues, it's purely just upgrading between the versions.

@gkrenn
Copy link
Contributor

gkrenn commented Feb 3, 2025

Hi! - Thanks for reaching out.

Version upgrades are tested in our test pipelines. To make sure I also run your commands manually to check if there could be a problem. Both the automated and manual tests worked without a problem.

Sadly I can't investigate your issue further as helm does not provide you with a proper error message. The error you see results from helm trying to rollback from version 1.4.0 to 1.3.2, maybe something slowed down your rollout and helm tried to rollback?

Anyway the error message is expected then, as the storage version changed between the releases and a downgrade from 1.4.0 to 1.3.2 is not supported.

As I can't reproduce your error I will close the issue, but feel free to open it again, in case you can provide more details.

@gkrenn gkrenn closed this as completed Feb 3, 2025
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