Skip to content

Commit 71aa60e

Browse files
committed
Azure self-hosted runners: show logs on failure
We're seeing intermittent `OSProvisioningTimedOut` errors on VM creation, which typically happens within 20-40 mins of the deployment hanging. Let's try and find out what's going wrong, so we can see if we need to fix things on our end. Ref: https://github.com/git-for-windows/git-for-windows-automation/actions/runs/11025772033/job/30621189230 Signed-off-by: Dennis Ameling <dennis@dennisameling.com>
1 parent 65c3a8e commit 71aa60e

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

.github/workflows/create-azure-self-hosted-runners.yml

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -158,6 +158,22 @@ jobs:
158158
template: ./azure-self-hosted-runners/azure-arm-template.json
159159
parameters: ./azure-self-hosted-runners/azure-arm-template-example-parameters.json ${{ env.AZURE_ARM_PARAMETERS }}
160160
scope: resourcegroup
161+
162+
- name: Show some more information on failure
163+
if: failure()
164+
run: |
165+
echo "::group::VM status"
166+
az vm get-instance-view --resource-group ${{ secrets.AZURE_RESOURCE_GROUP }} --name ${{ steps.generate-vm-name.outputs.vm_name }} --query "instanceView.statuses"
167+
az vm get-instance-view --resource-group ${{ secrets.AZURE_RESOURCE_GROUP }} --name ${{ steps.generate-vm-name.outputs.vm_name }} --query "statuses"
168+
echo "::endgroup::"
169+
170+
echo "::group::Deployment logs"
171+
az group deployment show --resource-group ${{ secrets.AZURE_RESOURCE_GROUP }} --name deploy-${{ steps.generate-vm-name.outputs.vm_name }}
172+
echo "::endgroup::"
173+
174+
echo "::group::Extension logs"
175+
az vm extension show --resource-group ${{ secrets.AZURE_RESOURCE_GROUP }} --vm-name ${{ steps.generate-vm-name.outputs.vm_name }} --name CustomScriptExtension
176+
echo "::endgroup::"
161177
162178
- name: Show post-deployment script output
163179
env:

0 commit comments

Comments
 (0)