This message was deleted.
# generala
adamant-kite-43734
12/04/2023, 5:39 PMThis message was deleted.
e
eager-refrigerator-66976
12/04/2023, 5:43 PMcapi-controller-manager Copy code
E1204 17:41:44.435523 1 controller.go:329] "Reconciler error" err="no matching Node for Machine \"custom-fbdc7789f02e\" in namespace \"fleet-default\": cannot find node with matching ProviderID" controller="machine" controllerGroup="<http://cluster.x-k8s.io|cluster.x-k8s.io>" controllerKind="Machine" Machine="fleet-default/custom-fbdc7789f02e" namespace="fleet-default" name="custom-fbdc7789f02e" reconcileID=330124c5-1ffb-4f7d-a618-94a976c62106
E1204 17:41:44.585423 1 controller.go:329] "Reconciler error" err="no matching Node for Machine \"custom-be9d831e6358\" in namespace \"fleet-default\": cannot find node with matching ProviderID" controller="machine" controllerGroup="<http://cluster.x-k8s.io|cluster.x-k8s.io>" controllerKind="Machine" Machine="fleet-default/custom-be9d831e6358" namespace="fleet-default" name="custom-be9d831e6358" reconcileID=63186033-4f57-4524-85af-2123a88f3a04eager-refrigerator-66976
12/04/2023, 5:51 PMmachine resource mentioned in the error still exists:
Copy code
k -n fleet-default get machine | grep custom-be9d831e6358
custom-be9d831e6358 rancher-euc1-te-test01 ip-172-29-196-238.eu-central-1.compute.internal aws:///eu-central-1a/i-0a82b430f14175488 Running 5h6m<http://nodes.management.cattle.io|nodes.management.cattle.io>eager-refrigerator-66976
12/04/2023, 6:05 PMthis is possibly related to https://github.com/kubernetes-sigs/cluster-api/issues/7237
c
creamy-rainbow-46562
12/04/2023, 7:26 PMI'm facing the same problem since 2.7.6... and keeps in 2.7.10
a
alert-king-94787
12/05/2023, 9:18 AMSame problem
e
eager-refrigerator-66976
12/05/2023, 11:01 AMI'll create a gh issue for this one.
eager-refrigerator-66976
12/05/2023, 7:29 PMcreated ticket: https://github.com/rancher/rancher/issues/43686
eager-refrigerator-66976
12/05/2023, 7:29 PMhappy to provide additional info if needed
w
wide-receptionist-90874
12/05/2023, 11:25 PM
yeah @eager-refrigerator-66976 from what I can tell it seems like you are hitting that situation.
the "happy path" for deleting nodes from a cluster by deleting the CAPI machine object and letting CAPI do the cleanup necessary including deleting the node object in the downstream cluster
wide-receptionist-90874
12/05/2023, 11:25 PM
we bumped CAPI version from 1.2.x to 1.4.x in 2.7.6 which makes sense as to why it is being hit since 2.7.6