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:
在 Rancher 版本 v2.11.0 - v2.11.4 和 v2.12.0 中，使用 Fleet 从 anOCI 注册表部署 Helm 图表时可能会遇到失败。即使底层注册表日志确认认证和文件拉取成功，这个问题仍然存在。舰队日志中的错误信息格式如下：

<span style="color:#000000"><span style="background-color:#ffffff"><span style="background-color:#efefef"><code>'failed to process bundle loading directory .chart/<hash>, app not logged in.'</code></span></span></span>

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+.
为解决此问题，用户应升级到已补丁的版本，Rancher v2.11 是 v2.11.5+，Rancher v2.12 是 v2.12.1+。

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.
根本原因是 Fleet v0.12.0 - v0.12.5 和 v0.13.0 中的一个 bug。该漏洞影响基于 OCI 图表的内部处理，导致部署失败，即使注册表认证成功，也会出现误导性的“未登录”错误。问题在 GitHub issue #3915 中被追踪。

• SUSE Rancher v2.11.0 - v2.11.4 and v2.12.0
  SUSE Rancher v2.11.0 - v2.11.4 和 v2.12.0
• A Fleet-deployed Helm chart from an OCI registry
  OCI 登记册中的舰队部署舵手图