Problem after upgrading zammad from version 3.2 to 3.4 about zammad-helm

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[monotek]

Have you tried to install 3.2, import the backup, update to 3.3 and then to 3.4?

[rmuehlbauer]

if you call it a upgrade to pull down the zammad 3.2 docker container(s) and bring up a 3.3/3.4 one(s) instead, then the answer is yes - I've tried to upgrade that way for several times.
I've also left a message over at community.zammad.com.
Long story short: I could solve my issues by running a db:init before importing the db dump - it seems like there is something missing in the db when you just export on 3.2 and import on 3.4... db:init could solve that issue.
As fas as of now, I was not able to find out where exactly the problem came from - only that db:init obviously solved it.
If we could find out the root cause of the problem, maybe zammad's postgresql init container could take care of this...

[monotek]

Sorry, we weren't able to reproduce...

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.