Creating AKS Cluster - vmssCSE Exit Code 124
TylerHaigh opened this issue · 2 comments
Describe the issue
When creating an AKS Cluster, adding nodepools, or scaling existing nodepools, the VMSS Provisioning fails with the following error
VM has reported a failure when processing extension 'vmssCSE'. Error message: "Enable failed: failed to execute command: command terminated with exit status=124 [stdout] { "ExitCode": "124", "Output": "+ '[' -f /opt/azure/containers/provision.complete ']'\n+ LOG_DIR=/var/log/azure/aks\n+ mkdir -p /var/log/azure/aks\n+ ln -s /var/log/azure/cluster-provision.log /var/log/azure/cluster-provision-cse-output.log /opt/azure/components.json /opt/azure/kube-proxy-images.json /opt/azure/manifest.json /opt/azure/cloud-init-files.paved /opt/azure/vhd-install.complete /var/log/azure/aks/\n+ python3 /opt/azure/containers/provision_redact_cloud_config.py --cloud-config-path /var/lib/cloud/instance/cloud-config.txt --output-path /var/log/azure/aks/cloud-config.txt\nRedacting secrets from write_file: /etc/kubernetes/sp.txt\nRedacting secrets from write_file: /var/lib/kubelet/bootstrap-kubeconfig\nDumping redacted cloud-config to: /var/log/azure/aks/cloud-config.txt\n++ lsb_release -r -s\n+ UBUNTU_RELEASE=18.04\n+ [[ 18.04 == \\1\\6\\.\\0\\4 ]]\n++ date\n++ hostname\n+ echo Thu Aug 25 02:50:47 UTC 2022,aks-apps-22067141-vmss000001, startcustomscript\n+ ERR_OUTBOUND_CONN_FAIL=50\n+ retrycmd_if_failure 100 1 10 curl -v --insecure --proxy-insecure https://mcr.microsoft.com/v2/", "Error": "", "ExecDuration": "900", "KernelStartTime": "Thu 2022-08-25 02:50:13 UTC", "CSEStartTime": "Thu Aug 25 02:50:47 UTC 2022", "GuestAgentStartTime": "Thu 2022-08-25 02:50:38 UTC", "SystemdSummary": "Startup finished in 749ms (firmware) + 12.134s (loader) + 6.039s (kernel) + 5min 23.501s (userspace) = 5min 42.424s\ngraphical.target reached after 22.496s in userspace", "BootDatapoints": { "KernelStartTime": "Thu 2022-08-25 02:50:13 UTC", "CSEStartTime": "Thu Aug 25 02:50:47 UTC 2022", "GuestAgentStartTime": "Thu 2022-08-25 02:50:38 UTC", "KubeletStartTime": "" } } [stderr] " More information on troubleshooting is available at https://aka.ms/VMExtensionCSELinuxTroubleshoot
AKS Engine Version*
Kubernetes Version
1.22.11
Gatekeeper Version
To Reproduce
Steps to reproduce the behavior:
- Login to Azure Portal
- Search for Kubernetes Services
- Select Kubernetes NodePool
- Select Scale or Add new Nodepool
Expected behavior
VMs for NodePool are provisioned ready for use
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
VMs are provisioned on an existing subnet which have network security group rules applied which affect provisioning
Please don't remove the text below
Notify @az-policy-kube
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it.
Resolved by reviewing NSG rules and ensuring Outbound Internet is open for ports 80,443