hundreds-evening-84071
07/13/2023, 5:27 PMrancher-vsphere-cpi-cloud-controller-manager
RKE2 v1.25 and also in v1.26
E0713 17:24:46.617584 1 node_controller.go:229] error syncing 'node1': failed to get provider ID for node node1 at cloudprovider: failed to get instance ID from cloud provider: VM Guest hostname is empty, requeuing
Is this a permissions issue in vsphere?thousands-camera-97808
07/17/2023, 7:29 PMbrainy-summer-72240
07/21/2023, 8:39 AMbrainy-summer-72240
07/21/2023, 8:39 AMbrainy-summer-72240
07/21/2023, 8:40 AMbrainy-summer-72240
07/21/2023, 8:41 AMbrainy-summer-72240
07/21/2023, 8:42 AMsteep-furniture-72588
07/21/2023, 4:46 PMsteep-furniture-72588
07/21/2023, 4:59 PMwooden-easter-8724
07/21/2023, 6:47 PMvalues.yaml
? No matter what format I’ve tried, I get a Helm error when trying to deploy the chart/template:
2023-07-21T14:47:52.234573800-04:00 Error: INSTALLATION FAILED: YAML parse error on cluster-template/templates/nodeconfig-vsphere.yaml: error converting YAML to JSON: yaml: line 45: did not find expected ',' or ']'
wooden-easter-8724
07/21/2023, 6:58 PMvappTransport: "com.vmware.guestInfo"
, the machine never progresses. (A similar configuration using an RKE1 node template works fine.)swift-sunset-4572
07/27/2023, 1:48 PM```Main PID: 1772 (rke2)
Tasks: 139
Memory: 1.8G
CPU: 1min 24.636s
CGroup: /system.slice/rke2-server.service
├─1772 "/usr/local/bin/rke2 server"
├─1797 containerd -c /var/lib/rancher/rke2/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/rancher/rke2/agent/containerd
├─1811 kubelet --volume-plugin-dir=/var/lib/kubelet/volumeplugins --file-check-frequency=5s --sync-frequency=30s --cloud-provider=external --cloud-config= --address=0.0.0.0 --anonymous-auth=false --authent>
├─1898 /var/lib/rancher/rke2/data/v1.26.6-rke2r1-8e8a9f4b16b3/bin/containerd-shim-runc-v2 -namespace k8s.io -id b92974ab30b1148fab78c2624c31eb44b50ab1d5b926c8cd844647349c135107 -address /run/k3s/containerd>
├─1984 /var/lib/rancher/rke2/data/v1.26.6-rke2r1-8e8a9f4b16b3/bin/containerd-shim-runc-v2 -namespace k8s.io -id 814f7b7f1f860789efd453ac8bfa793b48b1a561f5704d44c9092a66fb999e62 -address /run/k3s/containerd>
├─2078 /var/lib/rancher/rke2/data/v1.26.6-rke2r1-8e8a9f4b16b3/bin/containerd-shim-runc-v2 -namespace k8s.io -id 8314cd7f26eb53a3e865d92b1c0c66d79c5391de4556261420c3fd76bcc02207 -address /run/k3s/containerd>
├─2079 /var/lib/rancher/rke2/data/v1.26.6-rke2r1-8e8a9f4b16b3/bin/containerd-shim-runc-v2 -namespace k8s.io -id 5caf19098e89f5466118df43fe5a5d90181f3c1ca641a1217fa897a9442f4528 -address /run/k3s/containerd>
├─2236 /var/lib/rancher/rke2/data/v1.26.6-rke2r1-8e8a9f4b16b3/bin/containerd-shim-runc-v2 -namespace k8s.io -id 3667f8df7e783aa37fc5ff06356e21912b7555b44c257b221acd4aa719410c1b -address /run/k3s/containerd>
├─3314 /var/lib/rancher/rke2/data/v1.26.6-rke2r1-8e8a9f4b16b3/bin/containerd-shim-runc-v2 -namespace k8s.io -id c70ca041b43f8f8fdecae901beb37d40c5370a229888cb9dbe0ed06a3dbc94fb -address /run/k3s/containerd>
├─3779 /var/lib/rancher/rke2/data/v1.26.6-rke2r1-8e8a9f4b16b3/bin/containerd-shim-runc-v2 -namespace k8s.io -id 3ebc43b47311aa483cbe3857f48633306292e36d2901d9a92e7c36b9cff04ba6 -address /run/k3s/containerd>
└─4001 /var/lib/rancher/rke2/data/v1.26.6-rke2r1-8e8a9f4b16b3/bin/containerd-shim-runc-v2 -namespace k8s.io -id 0cfc1fd44cd126b40f9508f9c8e790f2620323a47053f1ed77396026d94af02b -address /run/k3s/containerd>
Jul 27 115816 vspherec1-pool1-dcfe19da-dtrkj rke2[1772]: time="2023-07-27T115816Z" level=info msg="Active TLS secret kube-system/rke2-serving (ver=380) (count 10): map[listener.cattle.io/cn-10.10.8.60:10.10.8.60 li>
Jul 27 115816 vspherec1-pool1-dcfe19da-dtrkj rke2[1772]: time="2023-07-27T115816Z" level=info msg="Running kube-proxy --cluster-cidr=10.42.0.0/16 --conntrack-max-per-core=0 --conntrack-tcp-timeout-close-wait=0s --c>```
Jul 27 11:58:16 vspherec1-pool1-dcfe19da-dtrkj rke2[1772]: time="2023-07-27T11:58:16Z" level=error msg="error syncing 'kube-system/rke2-calico': handler helm-controller-chart-registration: <http://helmcharts.helm.cattle.io|helmcharts.helm.cattle.io> \"r>
Jul 27 11:58:18 vspherec1-pool1-dcfe19da-dtrkj rke2[1772]: time="2023-07-27T11:58:18Z" level=error msg="error syncing 'kube-system/rke2-coredns': handler helm-controller-chart-registration: <http://helmcharts.helm.cattle.io|helmcharts.helm.cattle.io> \">
Jul 27 11:58:19 vspherec1-pool1-dcfe19da-dtrkj rke2[1772]: time="2023-07-27T11:58:19Z" level=error msg="error syncing 'kube-system/rke2-ingress-nginx': handler helm-controller-chart-registration: helmcharts.helm.cattle>
Jul 27 11:58:20 vspherec1-pool1-dcfe19da-dtrkj rke2[1772]: time="2023-07-27T11:58:20Z" level=error msg="error syncing 'kube-system/rke2-metrics-server': handler helm-controller-chart-registration: helmcharts.helm.cattl>
Jul 27 11:58:21 vspherec1-pool1-dcfe19da-dtrkj rke2[1772]: time="2023-07-27T11:58:21Z" level=error msg="error syncing 'kube-system/rke2-snapshot-controller-crd': handler helm-controller-chart-registration: helmcharts.h>
Jul 27 11:58:21 vspherec1-pool1-dcfe19da-dtrkj rke2[1772]: time="2023-07-27T11:58:21Z" level=error msg="error syncing 'kube-system/rke2-snapshot-controller': handler helm-controller-chart-registration: helmcharts.helm.>
Jul 27 11:58:21 vspherec1-pool1-dcfe19da-dtrkj rke2[1772]: time="2023-07-27T11:58:21Z" level=error msg="error syncing 'kube-system/rke2-snapshot-validation-webhook': handler helm-controller-chart-registration: helmchar>
```Jul 27 115859 vspherec1-pool1-dcfe19da-dtrkj rke2[1772]: time="2023-07-27T115859Z" level=info msg="Tunnel authorizer set Kubelet Port 10250"
lines 1-31/31 (END)```the highlighted lines it says that these are not found requeing. How should i proceed with this and get the cpi and csi working .
brainy-summer-72240
07/28/2023, 11:55 AMbored-plumber-53559
07/31/2023, 1:20 PMsteep-furniture-72588
08/01/2023, 3:22 AMshy-evening-11111
08/01/2023, 2:54 PMlimited-elephant-16797
08/03/2023, 7:03 AMRkecontrolplane was already initialized but no etcd machines exist that have plans, indicating the etcd plane has been entirely replaced. Restoration from etcd snapshot is required
bitter-shoe-85930
08/03/2023, 9:49 AM2023/08/03 06:50:39 [ERROR] [rkecluster] fleet-default/rke2-canal: error getting CAPI cluster no matching controller owner ref
2023/08/03 06:50:39 [ERROR] error syncing 'fleet-default/rke2-canal': handler rke-cluster: no matching controller owner ref, requeuing
2023/08/03 06:50:39 [ERROR] [rkecluster] fleet-default/rke2-canal: error getting CAPI cluster no matching controller owner ref
2023/08/03 06:50:39 [ERROR] error syncing 'fleet-default/rke2-canal': handler rke-cluster: no matching controller owner ref, requeuing
2023/08/03 06:50:39 [ERROR] [planner] rkecluster fleet-default/rke2-canal: error encountered during plan processing was no matching controller owner ref
2023/08/03 06:50:39 [ERROR] [rkecluster] fleet-default/rke2-canal: error getting CAPI cluster no matching controller owner ref
2023/08/03 06:50:39 [ERROR] error syncing 'fleet-default/rke2-canal': handler rke-cluster: no matching controller owner ref, requeuing
2023/08/03 06:50:39 [ERROR] [rkecluster] fleet-default/rke2-canal: error getting CAPI cluster no matching controller owner ref
2023/08/03 06:50:39 [ERROR] error syncing 'fleet-default/rke2-canal': handler rke-cluster: no matching controller owner ref, requeuing
2023/08/03 06:50:39 [ERROR] [rkecluster] fleet-default/rke2-canal: error getting CAPI cluster no matching controller owner ref
2023/08/03 06:50:39 [ERROR] error syncing 'fleet-default/rke2-canal': handler rke-cluster: no matching controller owner ref, requeuing
2023/08/03 06:50:39 [ERROR] error syncing 'fleet-default/rke2-canal': handler planner: no matching controller owner ref, requeuing
2023/08/03 06:50:39 [ERROR] [planner] rkecluster fleet-default/rke2-canal: error encountered during plan processing was no matching controller owner ref
2023/08/03 06:50:39 [ERROR] [rkecluster] fleet-default/rke2-canal: error getting CAPI cluster no matching controller owner ref
2023/08/03 06:50:39 [ERROR] error syncing 'fleet-default/rke2-canal': handler rke-cluster: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [ERROR] [planner] rkecluster fleet-default/rke2-canal: error encountered during plan processing was no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal': handler planner: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [ERROR] [planner] rkecluster fleet-default/rke2-canal: error encountered during plan processing was no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal': handler planner: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [ERROR] [planner] rkecluster fleet-default/rke2-canal: error encountered during plan processing was no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal': handler planner: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for infrastructure ready
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for infrastructure ready
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for infrastructure ready
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for infrastructure ready
2023/08/03 06:50:40 [ERROR] [CAPI] Reconciler error: Operation cannot be fulfilled on <http://machinedeployments.cluster.x-k8s.io|machinedeployments.cluster.x-k8s.io> "rke2-canal-pool1": the object has been modified; please apply your changes to the latest version and try again
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for infrastructure ready
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for at least one control plane, etcd, and worker node to be registered
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for at least one control plane, etcd, and worker node to be registered
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for at least one control plane, etcd, and worker node to be registered
2023/08/03 06:50:40 [ERROR] [rkebootstrap] fleet-default/rke2-canal-bootstrap-template-jw4bv: error getting machine by owner reference no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal-bootstrap-template-jw4bv': handler rke-bootstrap: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [ERROR] [rkebootstrap] fleet-default/rke2-canal-bootstrap-template-jw4bv: error getting machine by owner reference no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal-bootstrap-template-jw4bv': handler rke-bootstrap: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [ERROR] [machineprovision] fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt: error getting machine by owner reference: no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt': handler machine-provision: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [ERROR] [machineprovision] fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt: error getting machine by owner reference: no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt': handler machine-provision: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [ERROR] [rkebootstrap] fleet-default/rke2-canal-bootstrap-template-jw4bv: error getting machine by owner reference no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal-bootstrap-template-jw4bv': handler rke-bootstrap: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [ERROR] [machineprovision] fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt: error getting machine by owner reference: no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt': handler machine-provision: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [ERROR] [rkebootstrap] fleet-default/rke2-canal-bootstrap-template-jw4bv: error getting machine by owner reference no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal-bootstrap-template-jw4bv': handler rke-bootstrap: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [ERROR] [machineprovision] fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt: error getting machine by owner reference: no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt': handler machine-provision: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for at least one control plane, etcd, and worker node to be registered
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for at least one control plane, etcd, and worker node to be registered
2023/08/03 06:50:40 [ERROR] [machineprovision] fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt: error getting machine by owner reference: no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt': handler machine-provision: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [ERROR] [rkebootstrap] fleet-default/rke2-canal-bootstrap-template-jw4bv: error getting machine by owner reference no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal-bootstrap-template-jw4bv': handler rke-bootstrap: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [ERROR] [machineprovision] fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt: error getting machine by owner reference: no matching controller owner ref
2023/08/03 06:50:40 [ERROR] error syncing 'fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt': handler machine-provision: no matching controller owner ref, requeuing
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for viable init node
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for viable init node
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for viable init node
2023/08/03 06:50:40 [INFO] EnsureSecretForServiceAccount: waiting for secret [rke2-canal-bootstrap-template-jw4bv-machine-bootstrapz5jv] to be populated with token
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for viable init node
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for viable init node
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for viable init node
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for viable init node
2023/08/03 06:50:40 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for viable init node
2023/08/03 06:50:41 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for viable init node
2023/08/03 06:50:41 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for viable init node
2023/08/03 06:50:41 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for viable init node
2023/08/03 06:50:41 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for viable init node
2023/08/03 06:50:49 [INFO] [planner] rkecluster fleet-default/rke2-canal: waiting: waiting for viable init node
2023/08/03 06:50:50 [INFO] [machineprovision] fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt: reconciling machine job
2023/08/03 06:50:50 [INFO] [machineprovision] fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt: reconciling machine job
2023/08/03 06:50:50 [INFO] [machineprovision] fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt: reconciling machine job
2023/08/03 06:50:50 [INFO] [machineprovision] fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt: reconciling machine job
2023/08/03 06:50:50 [INFO] [machineprovision] fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt: reconciling machine job
2023/08/03 06:50:50 [INFO] [machineprovision] fleet-default/rke2-canal-pool1-bb5a7e33-qb9zt: reconciling machine job
bitter-shoe-85930
08/03/2023, 9:50 AMworried-yak-19329
08/03/2023, 11:27 PMlimited-elephant-16797
08/08/2023, 8:38 AMswift-sunset-4572
08/08/2023, 2:20 PMtall-traffic-61849
08/10/2023, 10:31 AMworried-yak-19329
08/15/2023, 8:02 PMhttps://www.virtualizationhowto.com/wp-content/uploads/2022/01/The-add-cluster-screen-in-Rancher-including-the-node-template-button.png▾
bitter-shoe-85930
08/24/2023, 4:39 PMbitter-shoe-85930
08/24/2023, 4:54 PMError while applying agent YAML, it will be retried automatically: exit status 1, Error from server (NotFound): the server could not find the requested resource
. Any ideas how to tshoot this issue further?
2023/08/24 15:41:38 [ERROR] error syncing '_all_': handler user-controllers-controller: userControllersController: failed to set peers for key _all_: failed to start user controllers for cluster c-m-n8z49bk5: ClusterUnavailable 503: cluster not found, requeuing
2023/08/24 15:41:51 [ERROR] Error during subscribe websocket: close sent
2023/08/24 15:42:08 [ERROR] error syncing '_all_': handler user-controllers-controller: userControllersController: failed to set peers for key _all_: failed to start user controllers for cluster c-m-n8z49bk5: ClusterUnavailable 503: cluster not found, requeuing
2023/08/24 15:42:38 [ERROR] error syncing '_all_': handler user-controllers-controller: userControllersController: failed to set peers for key _all_: failed to start user controllers for cluster c-m-n8z49bk5: ClusterUnavailable 503: cluster not found, requeuing
2023/08/24 15:43:04 [INFO] EnsureSecretForServiceAccount: waiting for secret [cluster-d9309f-bootstrap-template-v6f6n-machine-plan-tokengxw5k] to be populated with token
limited-elephant-16797
08/28/2023, 3:50 PMhelpful-hospital-59207
09/06/2023, 8:32 PMswift-sunset-4572
09/11/2023, 6:07 AMbrainy-summer-72240
09/11/2023, 3:42 PM