I want to use Rancher as edge orchestration tool.
My Rancher server setup:
- Rancher version: 2.6 - fresh installation
- Installation option (Docker install/Helm Chart): Docker install on an Edge (single node) system
When installing Longhorn from "Cluster Tools" and default settings, installation fails after 10 minutes with these logs (I tried this several times):
helm upgrade --install=true --namespace=longhorn-system --timeout=10m0s --values=/home/shell/helm/values-longhorn-crd-100.1.1-up1.2.3.yaml --version=100.1.1+up1.2.3 --wait=true longhorn-crd /home/shell/helm/longhorn-crd-100.1.1-up1.2.3.tgz
checking 15 resources for changes
Looks like there are no changes for CustomResourceDefinition "engines.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "replicas.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "settings.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "volumes.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "engineimages.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "nodes.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "instancemanagers.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "sharemanagers.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "backingimages.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "backingimagemanagers.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "backingimagedatasources.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "backuptargets.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "backupvolumes.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "backups.longhorn.io"
Looks like there are no changes for CustomResourceDefinition "recurringjobs.longhorn.io"
beginning wait for 15 resources with timeout of 10m0s
Release "longhorn-crd" has been upgraded. Happy Helming!
NAME: longhorn-crd
LAST DEPLOYED: Mon Dec 27 18:41:27 2021
NAMESPACE: longhorn-system
STATUS: deployed
REVISION: 2
TEST SUITE: None
---------------------------------------------------------------------
SUCCESS: helm upgrade --install=true --namespace=longhorn-system --timeout=10m0s --values=/home/shell/helm/values-longhorn-crd-100.1.1-up1.2.3.yaml --version=100.1.1+up1.2.3 --wait=true longhorn-crd /home/shell/helm/longhorn-crd-100.1.1-up1.2.3.tgz
---------------------------------------------------------------------
helm upgrade --install=true --namespace=longhorn-system --timeout=10m0s --values=/home/shell/helm/values-longhorn-100.1.1-up1.2.3.yaml --version=100.1.1+up1.2.3 --wait=true longhorn /home/shell/helm/longhorn-100.1.1-up1.2.3.tgz
Release "longhorn" does not exist. Installing it now.
W1227 18:41:30.709333 40 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
creating 18 resource(s)
W1227 18:41:30.798738 40 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
beginning wait for 18 resources with timeout of 10m0s
Deployment is not ready: longhorn-system/longhorn-driver-deployer. 0 out of 1 expected pods are ready
Deployment is not ready: longhorn-system/longhorn-driver-deployer. 0 out of 1 expected pods are ready
Deployment is not ready: longhorn-system/longhorn-driver-deployer. 0 out of 1 expected pods are ready
...
Error: timed out waiting for the condition
How can I fix this? What am I missing?
