Skip to content

Known issues#

This section describes the MSR known issues with available workarounds, along with current product limitations:

Helm upgrade with --reuse-values fails#

Upgrading MSR with Helm using the --reuse-values flag fails with the following error:

Error: UPGRADE FAILED: template:
msr/templates/migration/migration-svc.yaml:1:14: executing
"msr/templates/migration/migration-svc.yaml" at
<.Values.migration.enabled>: nil pointer evaluating interface {}.enabled

This issue occurs because releases before 4.13.6 do not include a migration values key. When --reuse-values carries forward a configuration that has no migration key, the chart template dereferences the missing key without a nil check, and the upgrade fails before any cluster changes are made.

This issue does not affect new MSR installations, because a new installation does not reuse prior Helm values.

Workaround

Use --reset-then-reuse-values instead of --reuse-values when upgrading to MSR 4.13.6 or later:

helm upgrade msr4 oci://<registry>/msr --version 4.13.6 \
  --reset-then-reuse-values \
  --set redis.external.addr=<new-address> \
  --set redis.external.existingSecret=<secret>

Configuration audit log written to audit log on configuration change#

Severity Level: Medium

MSR writes the configuration payload (ldap_search_password and oidc_client_secret) to audit log when the configuration changes.

Workaround:

Disable audit logging in MSR system settings.