Skip to content

Fleet Helm OCI deployments fail in Rancher v2.11.0 - v2.11.4 and v2.12.0

Article Number: 000021886

Environment

  • SUSE Rancher v2.11.0 - v2.11.4 and v2.12.0
  • A Fleet-deployed Helm chart from an OCI registry

Situation

In Rancher versions v2.11.0 - v2.11.4 and v2.12.0 you may encounter a failure when deploying Helm charts from an OCI registry using Fleet. This issue occurs even when the underlying registry logs confirm that authentication and artifact pulls are successful. The error message in the Fleet logs will be of the format:

'failed to process bundle loading directory .chart/<hash>, app not logged in.'

Cause

The root cause is a bug in Fleet v0.12.0 - v0.12.5 and v0.13.0. This bug affects the internal processing of OCI-based charts, causing the deployment to fail with a misleading "not logged in" error even where registry authentication was successful. The problem was tracked in GitHub issue #3915.

Resolution

To resolve this issue, users should upgrade to a patched version, for Rancher v2.11 this is v2.11.5+, for Rancher v2.12 this is v2.12.1+.