Fix RabbitMQ log output with Vault configured #1971
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit fixes the CI failure which tests the following example: https://github.com/rabbitmq/cluster-operator/tree/main/docs/examples/vault-default-user
RabbitMQ crashed at startup as follows:
The problem was that with Vault configured the mount in
cluster-operator/internal/resource/statefulset.go
Line 876 in 575cfac
https://github.com/docker-library/rabbitmq/blob/master/conf.d/10-defaults.conf containing the setting
Without any vault, the config directory in the RabbitMQ pod looks as follows:
With vault configured, the config directory in the RabbitMQ pod looks as follows:
This commit fixes the issue by adding
to file
10-operatorDefaults.conf.There is no harm if this setting is defined twice in different files in the
/etc/rabbitmq/conf.ddirectory. The last one wins.