little-dress-1357603/15/2023, 11:41 PM
user password, and allow console login..
hundreds-evening-8407103/15/2023, 11:52 PM
salmon-rainbow-3506503/16/2023, 2:15 PM
kind-nest-2331103/16/2023, 9:44 PM
quaint-alarm-789303/17/2023, 4:55 PM
lively-zoo-4038103/20/2023, 9:30 AM
lively-zoo-4038103/20/2023, 11:46 AM
lively-zoo-4038103/20/2023, 11:49 AM
lively-zoo-4038103/20/2023, 11:51 AM
lively-zoo-4038103/20/2023, 11:52 AM
lively-zoo-4038103/20/2023, 11:54 AM
lively-zoo-4038103/20/2023, 12:59 PM
Normal Pulling 39m (x2 over 40m) kubelet Pulling image "rancher/harvester-cluster-repo:v1.1.1"
Normal BackOff 39m (x3 over 40m) kubelet Back-off pulling image "rancher/harvester-cluster-repo:v1.1.1"
Warning Failed 39m (x3 over 40m) kubelet Error: ImagePullBackOff
Normal Pulling 37m (x4 over 39m) kubelet Pulling image "rancher/harvester-cluster-repo:v1.1.1"
Warning Failed 37m (x4 over 39m) kubelet Failed to pull image "rancher/harvester-cluster-repo:v1.1.1": rpc error: code = Unknown desc = failed to pull and unpack image "<http://docker.io/rancher/harvester-cluster-repo:v1.1.1|docker.io/rancher/harvester-cluster-repo:v1.1.1>": failed to resolve reference "<http://docker.io/rancher/harvester-cluster-repo:v1.1.1|docker.io/rancher/harvester-cluster-repo:v1.1.1>": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Warning Failed 37m (x4 over 39m) kubelet Error: ErrImagePull
Warning Failed 37m (x6 over 38m) kubelet Error: ImagePullBackOff
Normal BackOff 4m6s (x154 over 38m) kubelet Back-off pulling image "rancher/harvester-cluster-repo:v1.1.1"
lively-zoo-4038103/21/2023, 9:33 AM
lively-zoo-4038103/21/2023, 10:48 AM
lively-zoo-4038103/21/2023, 11:06 AM
refined-analyst-889803/21/2023, 3:32 PM
waiting for viable init nodeConditions log:
[Disconnected] Cluster agent is not connected
little-dress-1357603/21/2023, 3:59 PM
refined-analyst-889803/21/2023, 5:08 PM
rough-teacher-8837203/22/2023, 4:27 PM
stale-painting-8020303/22/2023, 11:19 PM
refined-analyst-889803/23/2023, 1:26 AM
appears. There must be another step. I see this in StorageClass doc:
Different Longhorn StorageClasses might map to replica policies, or to node schedule policies, or disk schedule policies determined by the cluster administrators
quaint-alarm-789303/23/2023, 4:46 AM
i imagine because my harvester cluster has a self-signed cert. any ideas on how to fix this? seems like my best bet is a custom-cluster for the provider, but i have no idea how to get the k3s or rke2 guest k8s cluster to trust harvester vip
"<https://192.168.5.100/k8s/clusters/local/apis/kubevirt.io/v1/namespaces/k8s/virtualmachines/k3s-m1>": x509: certificate signed by unknown authority
stale-painting-8020303/23/2023, 8:44 PM
little-dress-1357603/24/2023, 12:25 AM
refined-analyst-889803/24/2023, 2:55 PM
is answering lease requests originating from the attached LAN of the Harvester host's metal NIC. The VM network uses the default mgmt cluster network.
little-dress-1357603/24/2023, 10:51 PM
# dmidecode -s system-serial-number Not Specified # dmidecode -s system-product-nme None
refined-analyst-889803/25/2023, 2:51 AM
waiting for viable init nodeThe nodes are launched, but the console only shows a cloud-init error until the pool is eventually deleted. Wash, rinse, repeat. How can I diagnose the node condition that Rancher is waiting for?
refined-analyst-889803/26/2023, 11:01 PM
square-crayon-5141403/27/2023, 1:45 PM