Rancher Prime v2.12.1 scc-operator bug fix for v0.1.0 image

Rancher Prime v2.12.1 released with a new scc-operator feature to register Rancher Manager with the SCC. There is a bug in the initial version of the scc-operator image tag that is shipped with Rancher Prime v2.12.1 that will prevent all registrations from succeeding.

The error seen should look like:

non-recoverable HTTP error encountered; to reregister Rancher, resolve
connection issues then try again. Original error: API error: No product
found on SCC for: rancher v2.12.1 unknown <YOUR REG CODE> json
api/connect/v4/systems/products activate (code: 422)

To resolve this bug a new image for scc-operator was produces, which includes a fix. The issue has been resolved in v0.1.2 and will be included in subsequent releases.

Patching Rancher Prime v2.12.1

The image tag used for the SCC Operator is managed by a Rancher Setting called scc-operator-image. This Setting value can be modified in order to update in-place without a full Rancher update.

In order to update to the fixed scc-operator image with Rancher Prime v2.12.1 run:

kubectl patch setting scc-operator-image --type=merge -p '{"value":"rancher/scc-operator:v0.1.2"}'

Upgrading from Rancher Prime v2.12.1 to future releases

Users who upgrade to v2.12.1 and apply the path will need to revert the Setting modification when upgrading past v2.12.1. This will ensure that on v2.12.2 (for instance) your SCC Operator image will update to the newest version with that release.

To revert back to the default SCC Operator Image:

kubectl patch setting scc-operator-image --type=merge -p '{"value":""}'