[bitnami/mastodon] Change to improve init-job stability broke the init-job

[ajguyot]

Name and Version

bitnami/mastodon 6.2.10

What architecture are you using?

amd64

What steps will reproduce the bug?

Attempt a Helm upgrade from v6.2.9 to v6.2.10

Are you using any custom parameters or values?

I'm using an external secret for S3, perhaps that's the issue? The broken PR seems to show an expectation that the S3 secret is present in the values.yaml. However the error logs wouldn't make me think this is the problem but I'm not sure how better to debug.

What is the expected behavior?

The upgrade completes successfully.

What do you see instead?

init-job pod fails with exit code 127.

Logs state only the following:

Defaulted container "migrate-and-create-admin" out of: migrate-and-create-admin, mastodon-assets-precompile, copy-assets-dir (init), wait-for-s3 (init)
Error from server (BadRequest): container "migrate-and-create-admin" in pod "mastodon-init-knms2" is waiting to start: PodInitializing

Additional information

PR that triggered the issue is #28553