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 from 4.1.0 to 4.2.0 failing: mapping key "name" already defined #196

Closed
m-a-w-i opened this issue Apr 24, 2024 · 4 comments
Closed

Comments

@m-a-w-i
Copy link

m-a-w-i commented Apr 24, 2024

When upgrading from helm chart 4.1.0 to 4.2.0 ran into the issue:

reconciliation failed: Helm upgrade failed: error while running post render on files: map[string]interface (nil): yaml: unmarshal errors: line 150: mapping key "name" already defined at line 148

From what I see this is, because the key name is used twice for the new tmp volumeMount in the statefulset template

@bokysan
Copy link
Owner

bokysan commented Apr 24, 2024

You are correct. Weird that this was not caught by automated tests.

I'll fix that ASAP.

m-a-w-i added a commit to m-a-w-i/docker-postfix that referenced this issue Apr 24, 2024
@bokysan
Copy link
Owner

bokysan commented Apr 24, 2024

This commit should have resolved the issue.

Can you please check the :edge version (once it compiles) if it's still giving you the problems?

If no, I will publish a fix in the next few hours.

@m-a-w-i m-a-w-i changed the title Helm upgrade from 4.1.8 to 4.2.0 failing: mapping key "name" already defined Helm upgrade from 4.1.0 to 4.2.0 failing: mapping key "name" already defined Apr 24, 2024
@m-a-w-i
Copy link
Author

m-a-w-i commented Apr 24, 2024

Thanks for the quick fix!
Unfortunately I don't have an environment available, where I can easily run such tests. A released fix I should be able to easily test.

@m-a-w-i
Copy link
Author

m-a-w-i commented Apr 24, 2024

Thanks for the release. I can confirm that it is working.

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