You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if we use default databases in chart and change clusterDomain from default "cluster.local", we have some error on non installed variables
example:
Error: UPGRADE FAILED: execution error at (oncall/charts/rabbitmq/templates/statefulset.yaml:37:28):
PASSWORDS ERROR: You must provide your current passwords when upgrading the release.
Note that even after reinstallation, old credentials may be needed as they may be kept in persistent volume claims.
Further information can be obtained at https://docs.bitnami.com/general/how-to/troubleshoot-helm-chart-issues/#credential-errors-while-upgrading-chart-releases
'auth.password' must not be empty, please add '--set auth.password=$RABBITMQ_PASSWORD' to the command. To get the current value:
export RABBITMQ_PASSWORD=$(kubectl get secret --namespace "grafana-oncall" grafana-oncall-rabbitmq -o jsonpath="{.data.rabbitmq-password}" | base64 --decode)
in turn, setting this value does not work, because dependent charts are installed with priority while setting their own oncall
The text was updated successfully, but these errors were encountered:
if we use default databases in chart and change clusterDomain from default "cluster.local", we have some error on non installed variables
example:
Error: UPGRADE FAILED: execution error at (oncall/charts/rabbitmq/templates/statefulset.yaml:37:28):
PASSWORDS ERROR: You must provide your current passwords when upgrading the release.
Note that even after reinstallation, old credentials may be needed as they may be kept in persistent volume claims.
Further information can be obtained at https://docs.bitnami.com/general/how-to/troubleshoot-helm-chart-issues/#credential-errors-while-upgrading-chart-releases
in turn, setting this value does not work, because dependent charts are installed with priority while setting their own oncall
The text was updated successfully, but these errors were encountered: