· 6 years ago · Jun 29, 2019, 02:48 PM
1```
2ace@ace-x1:~/go/src/sigs.k8s.io/cluster-api-provider-azure$ kubectl logs azure-provider-controller-manager-0 -n azure-provider-system -f
3I0618 01:58:25.893921 1 plugins.go:39] Registered cluster provisioner "azure"
4I0618 01:58:25.898359 1 reflector.go:131] Starting reflector *v1alpha1.Cluster (10m0s) from sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126
5I0618 01:58:25.898432 1 reflector.go:169] Listing and watching *v1alpha1.Cluster from sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126
6I0618 01:58:25.898682 1 reflector.go:131] Starting reflector *v1alpha1.Machine (10m0s) from sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126
7I0618 01:58:25.898737 1 reflector.go:169] Listing and watching *v1alpha1.Machine from sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126
8I0618 01:58:26.197648 1 cluster_controller.go:90] Running reconcile Cluster for "capi"
9I0618 01:58:26.197800 1 machine_controller.go:113] Reconciling Machine "capi-controlplane-0"
10I0618 01:58:26.208126 1 cluster_controller.go:90] Running reconcile Cluster for "capi"
11I0618 01:58:26.208176 1 cluster_controller.go:139] reconciling cluster object capi triggers idempotent reconcile.
12I0618 01:58:26.208195 1 actuator.go:54] Reconciling cluster capi
13I0618 01:58:26.209689 1 reconciler.go:67] reconciling cluster capi
14I0618 01:58:26.209749 1 certificates.go:59] generating certificates
15I0618 01:58:26.209795 1 certificates.go:107] CreatePKIAssets
16I0618 01:58:26.209814 1 certs.go:37] creating PKI assets
17I0618 01:58:26.380368 1 machine_controller.go:113] Reconciling Machine "capi-controlplane-0"
18I0618 01:58:26.480480 1 machine_controller.go:149] Failed to add finalizers to machine "capi-controlplane-0": Operation cannot be fulfilled on machines.cluster.k8s.io "capi-controlplane-0": the object has been modified; please apply your changes to the latest version and try again
19I0618 01:58:27.480976 1 machine_controller.go:113] Reconciling Machine "capi-controlplane-0"
20I0618 01:58:27.481004 1 actuator.go:153] Checking if machine capi-controlplane-0 for cluster capi exists
21I0618 01:58:29.197782 1 machine_controller.go:222] Reconciling machine object capi-controlplane-0 triggers idempotent create.
22I0618 01:58:29.197822 1 actuator.go:74] Creating machine capi-controlplane-0 for cluster capi
23I0618 01:58:29.880339 1 reconciler.go:260] Machine capi-controlplane-0 should join the controlplane: false
24E0618 01:58:30.038157 1 actuator.go:84] failed to reconcile machine capi-controlplane-0 for cluster capi: failed to create nic capi-controlplane-0-nic for machine capi-controlplane-0: unable to create VM network interface: subnet capi-controlplane-subnet not found: network.SubnetsClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceGroupNotFound" Message="Resource group 'capi-fix' could not be found."
25E0618 01:58:30.080422 1 machine_scope.go:138] [machinescope] failed to update machine "capi-controlplane-0" in namespace "default": Operation cannot be fulfilled on machines.cluster.k8s.io "capi-controlplane-0": the object has been modified; please apply your changes to the latest version and try again
26I0618 01:58:30.080496 1 machine_controller.go:225] Actuator returned requeue-after error: requeue in: 1m0s
27I0618 01:58:30.080650 1 machine_controller.go:113] Reconciling Machine "capi-controlplane-0"
28I0618 01:58:30.080691 1 actuator.go:153] Checking if machine capi-controlplane-0 for cluster capi exists
29[certs] Generating "etcd/ca" certificate and key
30I0618 01:58:30.592612 1 machine_controller.go:222] Reconciling machine object capi-controlplane-0 triggers idempotent create.
31I0618 01:58:30.592788 1 actuator.go:74] Creating machine capi-controlplane-0 for cluster capi
32I0618 01:58:31.115581 1 reconciler.go:260] Machine capi-controlplane-0 should join the controlplane: false
33E0618 01:58:31.380486 1 actuator.go:84] failed to reconcile machine capi-controlplane-0 for cluster capi: failed to create nic capi-controlplane-0-nic for machine capi-controlplane-0: unable to create VM network interface: subnet capi-controlplane-subnet not found: network.SubnetsClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceGroupNotFound" Message="Resource group 'capi-fix' could not be found."
34I0618 01:58:31.395056 1 machine_controller.go:225] Actuator returned requeue-after error: requeue in: 1m0s
35[certs] Generating "etcd/peer" certificate and key
36[certs] etcd/peer serving cert is signed for DNS names [fakenodecapi localhost] and IPs [10.0.0.1 127.0.0.1 ::1]
37[certs] Generating "etcd/server" certificate and key
38[certs] etcd/server serving cert is signed for DNS names [fakenodecapi localhost] and IPs [10.0.0.1 127.0.0.1 ::1]
39[certs] Generating "etcd/healthcheck-client" certificate and key
40[certs] Generating "apiserver-etcd-client" certificate and key
41[certs] Generating "ca" certificate and key
42[certs] Generating "apiserver-kubelet-client" certificate and key
43[certs] Generating "apiserver" certificate and key
44[certs] apiserver serving cert is signed for DNS names [fakenodecapi kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local capi-bd40d8bc.westus2.cloudapp.azure.com] and IPs [10.96.0.1 10.0.0.1 10.0.0.100]
45[certs] Generating "front-proxy-ca" certificate and key
46[certs] Generating "front-proxy-client" certificate and key
47[certs] valid certificates and keys now exist in "/tmp/cluster-api/capi/certs"
48I0618 01:58:47.689579 1 certs.go:72] creating a new public/private key files for signing service account users
49[certs] Generating "sa" key and public key
50I0618 01:58:53.196025 1 certificates.go:111] CreatePKIAssets success
51I0618 01:58:53.196047 1 certificates.go:117] CreateSACertificates
52I0618 01:58:53.196057 1 certs.go:72] creating a new public/private key files for signing service account users
53[certs] Using the existing "sa" key
54I0618 01:58:55.980364 1 certificates.go:121] CreateSACertificates success
55I0618 01:58:55.980391 1 certificates.go:212] CreateKubeconfigs admin kubeconfig
56I0618 01:58:55.980407 1 kubeconfig.go:92] creating kubeconfig file for admin.conf
57[kubeconfig] Writing "admin.conf" kubeconfig file
58I0618 01:58:58.592047 1 certificates.go:225] CreateKubeconfigs admin kubeconfig success
59I0618 01:58:58.592422 1 certificates.go:127] GetDiscoveryHashes
60I0618 01:58:58.594887 1 certificates.go:161] GetDiscoveryHashes success
61I0618 01:58:58.594925 1 certificates.go:100] successfully created certificates
62I0618 01:58:58.596776 1 groups.go:36] creating resource group capi-fix
63I0618 01:58:59.535166 1 groups.go:38] successfully created resource group capi-fix
64I0618 01:58:59.568376 1 virtualnetworks.go:71] creating vnet capi-vnet
65I0618 01:59:09.949662 1 virtualnetworks.go:94] successfully created vnet capi-vnet
66I0618 01:59:09.949709 1 securitygroups.go:61] using additional rules for control plane capi-controlplane-nsg
67I0618 01:59:09.949723 1 securitygroups.go:92] creating security group capi-controlplane-nsg
68I0618 01:59:20.381694 1 securitygroups.go:117] created security group capi-controlplane-nsg
69I0618 01:59:20.381747 1 securitygroups.go:92] creating security group capi-node-nsg
70I0618 01:59:30.080857 1 machine_controller.go:113] Reconciling Machine "capi-controlplane-0"
71I0618 01:59:30.080916 1 actuator.go:153] Checking if machine capi-controlplane-0 for cluster capi exists
72I0618 01:59:30.639052 1 machine_controller.go:222] Reconciling machine object capi-controlplane-0 triggers idempotent create.
73I0618 01:59:30.639091 1 actuator.go:74] Creating machine capi-controlplane-0 for cluster capi
74I0618 01:59:30.929004 1 reconciler.go:260] Machine capi-controlplane-0 should join the controlplane: false
75I0618 01:59:30.937354 1 securitygroups.go:117] created security group capi-node-nsg
76I0618 01:59:30.937397 1 routetables.go:56] creating route table capi-node-routetable
77E0618 01:59:31.141801 1 actuator.go:84] failed to reconcile machine capi-controlplane-0 for cluster capi: failed to create nic capi-controlplane-0-nic for machine capi-controlplane-0: unable to create VM network interface: subnet capi-controlplane-subnet not found: network.SubnetsClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="NotFound" Message="Resource /subscriptions/074434f8-16f6-44d4-b452-dcbb0e24a5f3/resourceGroups/capi-fix/providers/Microsoft.Network/virtualNetworks/capi-vnet/subnets/capi-controlplane-subnet not found." Details=[]
78I0618 01:59:31.156942 1 machine_controller.go:225] Actuator returned requeue-after error: requeue in: 1m0s
79I0618 01:59:41.354550 1 routetables.go:79] successfully created route table capi-node-routetable
80I0618 01:59:41.354617 1 subnets.go:79] getting nsg capi-controlplane-nsg
81I0618 01:59:41.542825 1 subnets.go:88] got nsg capi-controlplane-nsg
82I0618 01:59:41.542867 1 subnets.go:91] creating subnet capi-controlplane-subnet in vnet capi-vnet
83I0618 01:59:51.906851 1 subnets.go:115] successfully created subnet capi-controlplane-subnet in vnet capi-vnet
84I0618 01:59:51.906913 1 subnets.go:66] getting route table capi-node-routetable
85I0618 01:59:52.043586 1 subnets.go:75] sucessfully got route table capi-node-routetable
86I0618 01:59:52.043626 1 subnets.go:79] getting nsg capi-node-nsg
87I0618 01:59:52.204071 1 subnets.go:88] got nsg capi-node-nsg
88I0618 01:59:52.204108 1 subnets.go:91] creating subnet capi-node-subnet in vnet capi-vnet
89I0618 02:00:02.488620 1 subnets.go:115] successfully created subnet capi-node-subnet in vnet capi-vnet
90I0618 02:00:02.488664 1 internalloadbalancers.go:62] creating internal load balancer capi-internal-lb
91I0618 02:00:02.488679 1 internalloadbalancers.go:69] getting subnet capi-controlplane-subnet
92I0618 02:00:02.652247 1 internalloadbalancers.go:79] successfully got subnet capi-controlplane-subnet
93I0618 02:00:13.026414 1 internalloadbalancers.go:150] successfully created internal load balancer capi-internal-lb
94I0618 02:00:13.026454 1 publicips.go:58] creating public ip capi-bd40d8bc
95I0618 02:00:17.630954 1 publicips.go:93] successfully created public ip capi-bd40d8bc
96I0618 02:00:17.630999 1 publicloadbalancers.go:64] creating public load balancer capi-public-lb
97I0618 02:00:17.631011 1 publicloadbalancers.go:66] getting public ip capi-bd40d8bc
98I0618 02:00:17.984148 1 publicloadbalancers.go:76] successfully got public ip capi-bd40d8bc
99I0618 02:00:18.337304 1 publicloadbalancers.go:187] successfully created public load balancer capi-public-lb
100I0618 02:00:18.337354 1 reconciler.go:155] successfully reconciled cluster capi
101I0618 02:00:18.381459 1 cluster_controller.go:90] Running reconcile Cluster for "capi"
102I0618 02:00:18.381480 1 cluster_controller.go:139] reconciling cluster object capi triggers idempotent reconcile.
103I0618 02:00:18.381486 1 actuator.go:54] Reconciling cluster capi
104I0618 02:00:18.383299 1 reconciler.go:67] reconciling cluster capi
105I0618 02:00:18.383322 1 certificates.go:59] generating certificates
106I0618 02:00:18.383339 1 certificates.go:107] CreatePKIAssets
107I0618 02:00:18.383346 1 certs.go:37] creating PKI assets
108[certs] Generating "etcd/ca" certificate and key
109[certs] Generating "apiserver-etcd-client" certificate and key
110[certs] Generating "etcd/peer" certificate and key
111[certs] etcd/peer serving cert is signed for DNS names [fakenodecapi localhost] and IPs [10.0.0.1 127.0.0.1 ::1]
112[certs] Generating "etcd/healthcheck-client" certificate and key
113I0618 02:00:31.157265 1 machine_controller.go:113] Reconciling Machine "capi-controlplane-0"
114I0618 02:00:31.157334 1 actuator.go:153] Checking if machine capi-controlplane-0 for cluster capi exists
115I0618 02:00:32.080467 1 machine_controller.go:222] Reconciling machine object capi-controlplane-0 triggers idempotent create.
116I0618 02:00:32.080512 1 actuator.go:74] Creating machine capi-controlplane-0 for cluster capi
117I0618 02:00:32.818380 1 reconciler.go:260] Machine capi-controlplane-0 should join the controlplane: false
118[certs] Generating "etcd/server" certificate and key
119[certs] etcd/server serving cert is signed for DNS names [fakenodecapi localhost] and IPs [10.0.0.1 127.0.0.1 ::1]
120I0618 02:00:33.916565 1 networkinterfaces.go:152] successfully created network interface capi-controlplane-0-nic
121[certs] Generating "ca" certificate and key
122I0618 02:00:43.887694 1 virtualmachines.go:70] getting nic capi-controlplane-0-nic
123I0618 02:00:44.281179 1 virtualmachines.go:79] got nic capi-controlplane-0-nic
124I0618 02:00:44.281219 1 virtualmachines.go:81] creating vm capi-controlplane-0
125[certs] Generating "apiserver" certificate and key
126[certs] apiserver serving cert is signed for DNS names [fakenodecapi kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local capi-bd40d8bc.westus2.cloudapp.azure.com] and IPs [10.96.0.1 10.0.0.1 10.0.0.100]
127[certs] Generating "apiserver-kubelet-client" certificate and key
128[certs] Generating "front-proxy-ca" certificate and key
129[certs] Generating "front-proxy-client" certificate and key
130[certs] valid certificates and keys now exist in "/tmp/cluster-api/capi/certs"
131I0618 02:01:00.194613 1 certs.go:72] creating a new public/private key files for signing service account users
132[certs] Generating "sa" key and public key
133I0618 02:01:02.385130 1 certificates.go:111] CreatePKIAssets success
134I0618 02:01:02.385164 1 certificates.go:117] CreateSACertificates
135I0618 02:01:02.385181 1 certs.go:72] creating a new public/private key files for signing service account users
136[certs] Using the existing "sa" key
137I0618 02:01:03.581772 1 certificates.go:121] CreateSACertificates success
138I0618 02:01:03.581790 1 certificates.go:212] CreateKubeconfigs admin kubeconfig
139I0618 02:01:03.581800 1 kubeconfig.go:92] creating kubeconfig file for admin.conf
140[kubeconfig] Writing "admin.conf" kubeconfig file
141I0618 02:01:07.498786 1 certificates.go:225] CreateKubeconfigs admin kubeconfig success
142I0618 02:01:07.498796 1 certificates.go:100] successfully created certificates
143I0618 02:01:07.499245 1 groups.go:36] creating resource group capi-fix
144I0618 02:01:08.369642 1 groups.go:38] successfully created resource group capi-fix
145I0618 02:01:08.436094 1 securitygroups.go:61] using additional rules for control plane capi-controlplane-nsg
146I0618 02:01:08.436134 1 securitygroups.go:92] creating security group capi-controlplane-nsg
147I0618 02:01:08.656363 1 securitygroups.go:117] created security group capi-controlplane-nsg
148I0618 02:01:08.656377 1 securitygroups.go:92] creating security group capi-node-nsg
149I0618 02:01:08.814401 1 securitygroups.go:117] created security group capi-node-nsg
150I0618 02:01:08.814453 1 routetables.go:56] creating route table capi-node-routetable
151I0618 02:01:08.982410 1 routetables.go:79] successfully created route table capi-node-routetable
152I0618 02:01:08.982458 1 subnets.go:79] getting nsg capi-controlplane-nsg
153I0618 02:01:09.166509 1 subnets.go:88] got nsg capi-controlplane-nsg
154I0618 02:01:09.166551 1 subnets.go:91] creating subnet capi-controlplane-subnet in vnet capi-vnet
155I0618 02:01:09.695031 1 subnets.go:115] successfully created subnet capi-controlplane-subnet in vnet capi-vnet
156I0618 02:01:09.695088 1 subnets.go:66] getting route table capi-node-routetable
157I0618 02:01:09.909573 1 subnets.go:75] sucessfully got route table capi-node-routetable
158I0618 02:01:09.909678 1 subnets.go:79] getting nsg capi-node-nsg
159I0618 02:01:10.082386 1 subnets.go:88] got nsg capi-node-nsg
160I0618 02:01:10.082439 1 subnets.go:91] creating subnet capi-node-subnet in vnet capi-vnet
161I0618 02:01:10.544243 1 subnets.go:115] successfully created subnet capi-node-subnet in vnet capi-vnet
162I0618 02:01:10.544291 1 internalloadbalancers.go:62] creating internal load balancer capi-internal-lb
163I0618 02:01:10.544308 1 internalloadbalancers.go:69] getting subnet capi-controlplane-subnet
164I0618 02:01:10.707777 1 internalloadbalancers.go:79] successfully got subnet capi-controlplane-subnet
165I0618 02:01:10.926797 1 internalloadbalancers.go:150] successfully created internal load balancer capi-internal-lb
166I0618 02:01:10.926837 1 publicips.go:58] creating public ip capi-bd40d8bc
167I0618 02:01:11.396930 1 publicips.go:93] successfully created public ip capi-bd40d8bc
168I0618 02:01:11.396979 1 publicloadbalancers.go:64] creating public load balancer capi-public-lb
169I0618 02:01:11.396999 1 publicloadbalancers.go:66] getting public ip capi-bd40d8bc
170I0618 02:01:11.527030 1 publicloadbalancers.go:76] successfully got public ip capi-bd40d8bc
171I0618 02:01:11.833240 1 publicloadbalancers.go:187] successfully created public load balancer capi-public-lb
172I0618 02:01:11.833298 1 reconciler.go:155] successfully reconciled cluster capi
173E0618 02:01:11.849526 1 scope.go:164] [scope] failed to store provider config for cluster "capi" in namespace "default": Operation cannot be fulfilled on clusters.cluster.k8s.io "capi": the object has been modified; please apply your changes to the latest version and try again
174I0618 02:01:11.849682 1 cluster_controller.go:90] Running reconcile Cluster for "capi"
175I0618 02:01:11.849720 1 cluster_controller.go:139] reconciling cluster object capi triggers idempotent reconcile.
176I0618 02:01:11.849737 1 actuator.go:54] Reconciling cluster capi
177I0618 02:01:11.854445 1 reconciler.go:67] reconciling cluster capi
178I0618 02:01:11.854491 1 certificates.go:59] generating certificates
179I0618 02:01:11.854529 1 certificates.go:107] CreatePKIAssets
180I0618 02:01:11.854545 1 certs.go:37] creating PKI assets
181[certs] Generating "ca" certificate and key
182[certs] Generating "apiserver" certificate and key
183[certs] apiserver serving cert is signed for DNS names [fakenodecapi kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local capi-bd40d8bc.westus2.cloudapp.azure.com] and IPs [10.96.0.1 10.0.0.1 10.0.0.100]
184[certs] Generating "apiserver-kubelet-client" certificate and key
185[certs] Generating "front-proxy-ca" certificate and key
186[certs] Generating "front-proxy-client" certificate and key
187[certs] Generating "etcd/ca" certificate and key
188[certs] Generating "apiserver-etcd-client" certificate and key
189[certs] Generating "etcd/server" certificate and key
190[certs] etcd/server serving cert is signed for DNS names [fakenodecapi localhost] and IPs [10.0.0.1 127.0.0.1 ::1]
191[certs] Generating "etcd/peer" certificate and key
192[certs] etcd/peer serving cert is signed for DNS names [fakenodecapi localhost] and IPs [10.0.0.1 127.0.0.1 ::1]
193[certs] Generating "etcd/healthcheck-client" certificate and key
194I0618 02:01:53.386655 1 certs.go:72] creating a new public/private key files for signing service account users
195[certs] valid certificates and keys now exist in "/tmp/cluster-api/capi/certs"
196[certs] Generating "sa" key and public key
197I0618 02:01:54.795071 1 certificates.go:111] CreatePKIAssets success
198I0618 02:01:54.795101 1 certificates.go:117] CreateSACertificates
199I0618 02:01:54.795114 1 certs.go:72] creating a new public/private key files for signing service account users
200[certs] Using the existing "sa" key
201I0618 02:01:58.685722 1 certificates.go:121] CreateSACertificates success
202I0618 02:01:58.685740 1 certificates.go:212] CreateKubeconfigs admin kubeconfig
203I0618 02:01:58.685750 1 kubeconfig.go:92] creating kubeconfig file for admin.conf
204[kubeconfig] Writing "admin.conf" kubeconfig file
205I0618 02:02:04.291178 1 certificates.go:225] CreateKubeconfigs admin kubeconfig success
206I0618 02:02:04.291213 1 certificates.go:100] successfully created certificates
207I0618 02:02:04.293468 1 groups.go:36] creating resource group capi-fix
208I0618 02:02:05.231730 1 groups.go:38] successfully created resource group capi-fix
209I0618 02:02:05.330070 1 securitygroups.go:61] using additional rules for control plane capi-controlplane-nsg
210I0618 02:02:05.330113 1 securitygroups.go:92] creating security group capi-controlplane-nsg
211I0618 02:02:05.582516 1 securitygroups.go:117] created security group capi-controlplane-nsg
212I0618 02:02:05.582572 1 securitygroups.go:92] creating security group capi-node-nsg
213I0618 02:02:05.735329 1 securitygroups.go:117] created security group capi-node-nsg
214I0618 02:02:05.735370 1 routetables.go:56] creating route table capi-node-routetable
215I0618 02:02:05.906052 1 routetables.go:79] successfully created route table capi-node-routetable
216I0618 02:02:05.906099 1 subnets.go:79] getting nsg capi-controlplane-nsg
217I0618 02:02:06.176413 1 subnets.go:88] got nsg capi-controlplane-nsg
218I0618 02:02:06.176458 1 subnets.go:91] creating subnet capi-controlplane-subnet in vnet capi-vnet
219I0618 02:02:06.657785 1 subnets.go:115] successfully created subnet capi-controlplane-subnet in vnet capi-vnet
220I0618 02:02:06.657863 1 subnets.go:66] getting route table capi-node-routetable
221I0618 02:02:06.778767 1 subnets.go:75] sucessfully got route table capi-node-routetable
222I0618 02:02:06.778817 1 subnets.go:79] getting nsg capi-node-nsg
223I0618 02:02:06.895798 1 subnets.go:88] got nsg capi-node-nsg
224I0618 02:02:06.895894 1 subnets.go:91] creating subnet capi-node-subnet in vnet capi-vnet
225I0618 02:02:07.383661 1 subnets.go:115] successfully created subnet capi-node-subnet in vnet capi-vnet
226I0618 02:02:07.383701 1 internalloadbalancers.go:62] creating internal load balancer capi-internal-lb
227I0618 02:02:07.383716 1 internalloadbalancers.go:69] getting subnet capi-controlplane-subnet
228I0618 02:02:07.451599 1 internalloadbalancers.go:79] successfully got subnet capi-controlplane-subnet
229I0618 02:02:07.781301 1 internalloadbalancers.go:150] successfully created internal load balancer capi-internal-lb
230I0618 02:02:07.781344 1 publicips.go:58] creating public ip capi-bd40d8bc
231I0618 02:02:08.226220 1 publicips.go:93] successfully created public ip capi-bd40d8bc
232I0618 02:02:08.226267 1 publicloadbalancers.go:64] creating public load balancer capi-public-lb
233I0618 02:02:08.226286 1 publicloadbalancers.go:66] getting public ip capi-bd40d8bc
234I0618 02:02:08.383232 1 publicloadbalancers.go:76] successfully got public ip capi-bd40d8bc
235I0618 02:02:08.718769 1 publicloadbalancers.go:187] successfully created public load balancer capi-public-lb
236I0618 02:02:08.718818 1 reconciler.go:155] successfully reconciled cluster capi
237I0618 02:02:15.005033 1 virtualmachines.go:177] successfully created vm capi-controlplane-0
238I0618 02:02:15.005100 1 startupscript.go:91] Machine capi-controlplane-0 is the first controlplane machine for cluster capi
239I0618 02:02:15.005589 1 virtualmachineextensions.go:59] creating vm extension startupScript
240
241I0618 02:07:15.489638 1 virtualmachineextensions.go:97] successfully created vm extension startupScript
242I0618 02:07:15.515484 1 machine_controller.go:113] Reconciling Machine "capi-controlplane-0"
243I0618 02:07:15.515543 1 actuator.go:153] Checking if machine capi-controlplane-0 for cluster capi exists
244I0618 02:07:16.187044 1 reconciler.go:342] Found vm for machine capi-controlplane-0
245I0618 02:07:16.280481 1 reconciler.go:165] Machine /subscriptions/074434f8-16f6-44d4-b452-dcbb0e24a5f3/resourceGroups/capi-fix/providers/Microsoft.Compute/virtualMachines/capi-controlplane-0 is running
246I0618 02:07:16.392331 1 reconciler.go:189] Setting machine capi-controlplane-0 nodeRef to capi-controlplane-0
247I0618 02:07:16.413037 1 machine_controller.go:207] Reconciling machine "capi-controlplane-0" triggers idempotent update
248I0618 02:07:16.413077 1 actuator.go:127] Updating machine capi-controlplane-0 for cluster capi.
249E0618 02:07:16.945224 1 machine_scope.go:138] [machinescope] failed to update machine "capi-controlplane-0" in namespace "default": Operation cannot be fulfilled on machines.cluster.k8s.io "capi-controlplane-0": the object has been modified; please apply your changes to the latest version and try again
250I0618 02:07:16.945358 1 machine_controller.go:113] Reconciling Machine "capi-controlplane-0"
251I0618 02:07:16.945423 1 actuator.go:153] Checking if machine capi-controlplane-0 for cluster capi exists
252I0618 02:07:17.435049 1 reconciler.go:342] Found vm for machine capi-controlplane-0
253I0618 02:07:17.467533 1 reconciler.go:165] Machine /subscriptions/074434f8-16f6-44d4-b452-dcbb0e24a5f3/resourceGroups/capi-fix/providers/Microsoft.Compute/virtualMachines/capi-controlplane-0 is running
254I0618 02:07:17.474346 1 machine_controller.go:207] Reconciling machine "capi-controlplane-0" triggers idempotent update
255I0618 02:07:17.474359 1 actuator.go:127] Updating machine capi-controlplane-0 for cluster capi.
256I0618 02:07:23.526008 1 cluster_controller.go:90] Running reconcile Cluster for "capi"
257I0618 02:07:23.526035 1 cluster_controller.go:139] reconciling cluster object capi triggers idempotent reconcile.
258I0618 02:07:23.526045 1 actuator.go:54] Reconciling cluster capi
259I0618 02:07:23.580170 1 reconciler.go:67] reconciling cluster capi
260I0618 02:07:23.580184 1 certificates.go:59] generating certificates
261I0618 02:07:23.580196 1 certificates.go:107] CreatePKIAssets
262I0618 02:07:23.580201 1 certs.go:37] creating PKI assets
263[certs] Generating "ca" certificate and key
264rpc error: code = Unknown desc = Error: No such container: 049a4a1b53470b94f0a997a59cf1931590db2c60ce4261b469d365554f93166a
265```