Why Can't I Upgrade My Rancher App from OCI Registry Using a Build Pipeline?

Rancher
1

I am using Rancher version 2.9.1 with OCI registries. I have successfully added and pushed images to Azure Container Registry (ACR). However, when I attempt to upgrade the last pushed image in my Rancher app using the command:
./rancher-v2.9.0/rancher app upgrade "${{ parameters.appName }}" "${{ parameters.appVersion }}"
the upgrade does not work, and the version does not update. While using the Rancher UI, I can refresh the repositories, and the updated version of the app is reflected correctly.

For example, when the docker repo is abc/abc-ci and version is 1.21.1, the command returns an error stating that the abc-ci at version 1.21.1 is not found.

OCI repository URL oci://xyz.azurecr.io/abc/abc-ci

Could you please help me troubleshoot this issue?

2

looks like you are hit by [BUG] Adding OCI Repositories to the Marketplace only works when specifying the full path to the chart · Issue #47115 · rancher/rancher · GitHub

3

No, actually the installed apps were not upgraded when I ran ./rancher-v2.6.7/rancher app upgrade ${{ parameters.appName }} --version ${{ parameters.appVersion }}, because Rancher removes legacy apps in newer versions, and the apps command no longer works. Additionally, the repositories were not refreshed when I tried to automate this operation from the build pipeline.

4

Look at the Rancher server logs for any additional error messages or warnings that might indicate why the upgrade is failing. You can usually find these logs in the container running Rancher or through the Rancher UI under the logging section.