https://rancher.com/ logo
Title
s

strong-shoe-72392

01/31/2023, 9:13 PM
Hello again! Are there any other resources that need to be installed to use the Elemental OS Upgrade capability besides the prerequisites here - https://elemental.docs.rancher.com/next/quickstart/#what-is-the-rancher-elemental-stack- ? I tried to perform an Elemental Teal OS Upgrade on a Raspberry Pi 4 (that successfully provisioned k3s using the Quickstart and raw image for RPi) using the following:
apiVersion: <http://elemental.cattle.io/v1beta1|elemental.cattle.io/v1beta1>
kind: ManagedOSImage
metadata:
  name: elemental-rpi-upgrade-demo
  namespace: fleet-default
spec:
  # Set to the new Elemental version you would like to upgrade to or track the latest tag
  osImage: "<http://registry.opensuse.org/isv/rancher/elemental/dev/teal53/15.4/rancher/elemental-teal/5.3:1.1.0-60.7|registry.opensuse.org/isv/rancher/elemental/dev/teal53/15.4/rancher/elemental-teal/5.3:1.1.0-60.7>"
  clusterTargets:
    - clusterName: elemental-rpi-cluster
My current version according to /etc/os-release is:
IMAGE_REPO="<http://registry.opensuse.org/isv/rancher/elemental/dev/teal53/15.4/rancher/elemental-teal/5.3|registry.opensuse.org/isv/rancher/elemental/dev/teal53/15.4/rancher/elemental-teal/5.3>"
IMAGE_TAG="1.0.0-40.2"
When applied, I see that Fleet tries to make a new bundle but errors out on what appears to be missing CRDs:
elemental-rpi-cluster-managed-system-agent
ErrApplied(1) [Cluster fleet-default/elemental-rpi-cluster: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "system-agent-upgrader" namespace: "cattle-system" from "": no matches for kind "Plan" in version "<http://upgrade.cattle.io/v1|upgrade.cattle.io/v1>" ensure CRDs are installed first, resource mapping not found for name: "system-agent-upgrader-windows" namespace: "cattle-system" from "": no matches for kind "Plan" in version "<http://upgrade.cattle.io/v1|upgrade.cattle.io/v1>" ensure CRDs are installed first]]
I even attempted to install the Rancher System-Upgrade-Controller into our Rancher Server/MCM cluster as it looked like it had some of those CRDs, but that didn't fix anything. Did I miss a step? Is this not yet supported for Raspberry Pis (although it seems to be failing before the bundle is created anyway)? As usual, any help is greatly appreciated!
h

high-morning-12231

01/31/2023, 9:48 PM
I believe that upgrades are not supported on ARM64 yet. This includes upgrades of k3s or rke2 as well. This is actively being worked on and I believe that this issue is the last blocker to supporting ARM more fully: https://github.com/rancher/rancher/issues/40215
s

strong-shoe-72392

01/31/2023, 9:50 PM
Thanks Andrew! Upgrades are supported on x86 for RKE2 and k3s currently though, correct? Or those may require the updated system-agent too?
h

high-morning-12231

01/31/2023, 9:50 PM
I'm a little confused by the error since it seems like the GH issue I linked would provide a different error but am not sure enough of the internals of the upgrade process
Yes, upgrades should work on x86_64
s

strong-shoe-72392

01/31/2023, 9:51 PM
I know our Rancher MCM is 2.7.0 and running Elemental Operator 1.1.1
h

high-morning-12231

01/31/2023, 9:52 PM
I'm still a little behind on versions for my demo setup but updates are a part of the automated QA
s

strong-shoe-72392

01/31/2023, 9:55 PM
Thanks again! I'll watch that GitHub issue and keep an eye on future releases. May have to go back to testing Elemental upgrades with VMs for the time being then.