Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): bump actions/setup-go from 3 to 5 #3909

Open
wants to merge 4 commits into
base: dev
Choose a base branch
from
+165 −148

chore(deps): bump actions/setup-go from 3 to 5

7342503
Select commit
Loading
Failed to load commit list.
Open

chore(deps): bump actions/setup-go from 3 to 5 #3909

chore(deps): bump actions/setup-go from 3 to 5
7342503
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Agentbaker E2E failed Oct 31, 2024 in 37m 50s

Build #20241031.2 had test failures

1 errors / 1 warnings

Details

Tests

  • Failed: 13 (25.00%)
  • Passed: 39 (75.00%)
  • Other: 0 (0.00%)
  • Total: 52

Annotations

Check failure on line 2799 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Build log #L2799 

Bash exited with code '1'.

Check failure on line 1 in Test_azurelinuxv2ChronyRestarts

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Test_azurelinuxv2ChronyRestarts 

Failed
Raw output 
    scenario_helpers_test.go:96: running scenario "Test_azurelinuxv2ChronyRestarts" with vhd: "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/AzureLinuxV2gen2/versions/1.1730361847.13188", tags {Name:Test_azurelinuxv2ChronyRestarts ImageName:AzureLinuxV2gen2 OS:azurelinux Arch:amd64 Airgap:false GPU:false WASM:false ServerTLSBootstrapping:false Scriptless:false}
    scenario_helpers_test.go:102: running scenario "Test_azurelinuxv2ChronyRestarts" with image "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/AzureLinuxV2gen2/versions/1.1730361847.13188" in aks cluster "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourcegroups/abe2e-westus3/providers/Microsoft.ContainerService/managedClusters/abe2e-kubenet-331fc"
    vmss.go:36: creating VMSS "abe2e-2024-10-31-2zi7-azurelinuxv2chronyrestarts" in resource group "MC_abe2e-westus3_abe2e-kubenet-331fc_westus3"
    scenario_helpers_test.go:110: vmss abe2e-2024-10-31-2zi7-azurelinuxv2chronyrestarts creation succeeded, proceeding with node readiness and pod checks...
    pollers.go:29: waiting for node abe2e-2024-10-31-2zi7-azurelinuxv2chronyrestarts to be ready
    pollers.go:57: node abe2e-2024-10-31-2zi7-azurelinuxv2chronyrestarts000000 is ready
    scenario_helpers_test.go:122: node abe2e-2024-10-31-2zi7-azurelinuxv2chronyrestarts is ready, proceeding with validation commands...
    scenario_helpers_test.go:129: 
        	Error Trace:	/mnt/vss/_work/1/s/e2e/scenario_helpers_test.go:129
        	            				/mnt/vss/_work/1/s/e2e/scenario_helpers_test.go:60
        	            				/mnt/vss/_work/1/s/e2e/scenario_test.go:137
        	Error:      	Received unexpected error:
        	            	while running live validator for node abe2e-2024-10-31-2zi7-azurelinuxv2chronyrestarts, unable to get non host debug pod name: failed to find non host debug pod on node abe2e-2024-10-31-2zi7-azurelinuxv2chronyrestarts
        	Test:       	Test_azurelinuxv2ChronyRestarts
    exec.go:74: executing command on remote VM at 10.224.0.207 of VMSS abe2e-2024-10-31-2zi7-azurelinuxv2chronyrestarts: "journalctl -u kubelet"
    exec.go:74: executing command on remote VM at 10.224.0.207 of VMSS abe2e-2024-10-31-2zi7-azurelinuxv2chronyrestarts: "cat /var/log/azure/cluster-provision-cse-output.log"
    exec.go:74: executing command on remote VM at 10.224.0.207 of VMSS abe2e-2024-10-31-2zi7-azurelinuxv2chronyrestarts: "sysctl -a"
    exec.go:74: executing command on remote VM at 10.224.0.207 of VMSS abe2e-2024-10-31-2zi7-azurelinuxv2chronyrestarts: "cat /var/log/azure/node-bootstrapper.log"
    exec.go:74: executing command on remote VM at 10.224.0.207 of VMSS abe2e-2024-10-31-2zi7-azurelinuxv2chronyrestarts: "cat /var/log/azure/cluster-provision.log"
    vmss.go:123: vmss "abe2e-2024-10-31-2zi7-azurelinuxv2chronyrestarts" deleted successfully

Check failure on line 1 in Test_azurelinuxv2gpu

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Test_azurelinuxv2gpu 

Failed
Raw output 
    scenario_helpers_test.go:96: running scenario "Test_azurelinuxv2gpu" with vhd: "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/AzureLinuxV2gen2/versions/1.1730361847.13188", tags {Name:Test_azurelinuxv2gpu ImageName:AzureLinuxV2gen2 OS:azurelinux Arch:amd64 Airgap:false GPU:true WASM:false ServerTLSBootstrapping:false Scriptless:false}
    scenario_helpers_test.go:102: running scenario "Test_azurelinuxv2gpu" with image "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/AzureLinuxV2gen2/versions/1.1730361847.13188" in aks cluster "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourcegroups/abe2e-westus3/providers/Microsoft.ContainerService/managedClusters/abe2e-kubenet-331fc"
    vmss.go:36: creating VMSS "abe2e-2024-10-31-9f09-azurelinuxv2gpu" in resource group "MC_abe2e-westus3_abe2e-kubenet-331fc_westus3"
    scenario_helpers_test.go:110: vmss abe2e-2024-10-31-9f09-azurelinuxv2gpu creation succeeded, proceeding with node readiness and pod checks...
    pollers.go:29: waiting for node abe2e-2024-10-31-9f09-azurelinuxv2gpu to be ready
    pollers.go:57: node abe2e-2024-10-31-9f09-azurelinuxv2gpu000000 is ready
    scenario_helpers_test.go:122: node abe2e-2024-10-31-9f09-azurelinuxv2gpu is ready, proceeding with validation commands...
I1031 15:49:02.320578  231585 request.go:700] Waited for 3.237809128s due to client-side throttling, not priority and fairness, request: GET:https://abe2e-kubenet-vj1lqils.hcp.westus3.azmk8s.io:443/api/v1/namespaces/default/pods/test-pod-abe2e-2024-10-31-iq5k-marinerv2customsysctls000000
    scenario_helpers_test.go:129: 
        	Error Trace:	/mnt/vss/_work/1/s/e2e/scenario_helpers_test.go:129
        	            				/mnt/vss/_work/1/s/e2e/scenario_helpers_test.go:60
        	            				/mnt/vss/_work/1/s/e2e/scenario_test.go:200
        	Error:      	Received unexpected error:
        	            	while running live validator for node abe2e-2024-10-31-9f09-azurelinuxv2gpu, unable to get non host debug pod name: failed to find non host debug pod on node abe2e-2024-10-31-9f09-azurelinuxv2gpu
        	Test:       	Test_azurelinuxv2gpu
    exec.go:74: executing command on remote VM at 10.224.0.155 of VMSS abe2e-2024-10-31-9f09-azurelinuxv2gpu: "cat /var/log/azure/cluster-provision.log"
    exec.go:74: executing command on remote VM at 10.224.0.155 of VMSS abe2e-2024-10-31-9f09-azurelinuxv2gpu: "journalctl -u kubelet"
    exec.go:74: executing command on remote VM at 10.224.0.155 of VMSS abe2e-2024-10-31-9f09-azurelinuxv2gpu: "cat /var/log/azure/cluster-provision-cse-output.log"
    exec.go:74: executing command on remote VM at 10.224.0.155 of VMSS abe2e-2024-10-31-9f09-azurelinuxv2gpu: "sysctl -a"
    exec.go:74: executing command on remote VM at 10.224.0.155 of VMSS abe2e-2024-10-31-9f09-azurelinuxv2gpu: "cat /var/log/azure/node-bootstrapper.log"
    vmss.go:123: vmss "abe2e-2024-10-31-9f09-azurelinuxv2gpu" deleted successfully

Check failure on line 1 in Test_marinerv2ARM64

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Test_marinerv2ARM64 

Failed
Raw output 
    scenario_helpers_test.go:96: running scenario "Test_marinerv2ARM64" with vhd: "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/CBLMarinerV2gen2arm64/versions/1.1730361968.607", tags {Name:Test_marinerv2ARM64 ImageName:CBLMarinerV2gen2arm64 OS:mariner Arch:arm64 Airgap:false GPU:false WASM:false ServerTLSBootstrapping:false Scriptless:false}
    scenario_helpers_test.go:102: running scenario "Test_marinerv2ARM64" with image "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/CBLMarinerV2gen2arm64/versions/1.1730361968.607" in aks cluster "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourcegroups/abe2e-westus3/providers/Microsoft.ContainerService/managedClusters/abe2e-kubenet-331fc"
    vmss.go:36: creating VMSS "abe2e-2024-10-31-uw7x-marinerv2arm64" in resource group "MC_abe2e-westus3_abe2e-kubenet-331fc_westus3"
    scenario_helpers_test.go:110: vmss abe2e-2024-10-31-uw7x-marinerv2arm64 creation succeeded, proceeding with node readiness and pod checks...
    pollers.go:29: waiting for node abe2e-2024-10-31-uw7x-marinerv2arm64 to be ready
    pollers.go:57: node abe2e-2024-10-31-uw7x-marinerv2arm64000000 is ready
    scenario_helpers_test.go:122: node abe2e-2024-10-31-uw7x-marinerv2arm64 is ready, proceeding with validation commands...
    scenario_helpers_test.go:129: 
        	Error Trace:	/mnt/vss/_work/1/s/e2e/scenario_helpers_test.go:129
        	            				/mnt/vss/_work/1/s/e2e/scenario_helpers_test.go:60
        	            				/mnt/vss/_work/1/s/e2e/scenario_test.go:316
        	Error:      	Received unexpected error:
        	            	while running live validator for node abe2e-2024-10-31-uw7x-marinerv2arm64, unable to get non host debug pod name: failed to find non host debug pod on node abe2e-2024-10-31-uw7x-marinerv2arm64
        	Test:       	Test_marinerv2ARM64
    exec.go:74: executing command on remote VM at 10.224.0.52 of VMSS abe2e-2024-10-31-uw7x-marinerv2arm64: "cat /var/log/azure/cluster-provision.log"
I1031 15:47:10.920860  231585 request.go:700] Waited for 4.464420995s due to client-side throttling, not priority and fairness, request: GET:https://abe2e-kubenet-vj1lqils.hcp.westus3.azmk8s.io:443/api/v1/namespaces/default/pods/test-pod-abe2e-2024-10-31-zoo3-ubuntu2204000000
    exec.go:74: executing command on remote VM at 10.224.0.52 of VMSS abe2e-2024-10-31-uw7x-marinerv2arm64: "journalctl -u kubelet"
    exec.go:74: executing command on remote VM at 10.224.0.52 of VMSS abe2e-2024-10-31-uw7x-marinerv2arm64: "cat /var/log/azure/cluster-provision-cse-output.log"
    exec.go:74: executing command on remote VM at 10.224.0.52 of VMSS abe2e-2024-10-31-uw7x-marinerv2arm64: "sysctl -a"
    exec.go:74: executing command on remote VM at 10.224.0.52 of VMSS abe2e-2024-10-31-uw7x-marinerv2arm64: "cat /var/log/azure/node-bootstrapper.log"
    vmss.go:123: vmss "abe2e-2024-10-31-uw7x-marinerv2arm64" deleted successfully

Check failure on line 1 in Test_marinerv2gpu

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Test_marinerv2gpu 

Failed
Raw output 
    scenario_helpers_test.go:96: running scenario "Test_marinerv2gpu" with vhd: "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/CBLMarinerV2gen2/versions/1.1730362027.21434", tags {Name:Test_marinerv2gpu ImageName:CBLMarinerV2gen2 OS:mariner Arch:amd64 Airgap:false GPU:true WASM:false ServerTLSBootstrapping:false Scriptless:false}
    scenario_helpers_test.go:102: running scenario "Test_marinerv2gpu" with image "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/CBLMarinerV2gen2/versions/1.1730362027.21434" in aks cluster "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourcegroups/abe2e-westus3/providers/Microsoft.ContainerService/managedClusters/abe2e-kubenet-331fc"
    vmss.go:36: creating VMSS "abe2e-2024-10-31-disy-marinerv2gpu" in resource group "MC_abe2e-westus3_abe2e-kubenet-331fc_westus3"
    scenario_helpers_test.go:110: vmss abe2e-2024-10-31-disy-marinerv2gpu creation succeeded, proceeding with node readiness and pod checks...
    pollers.go:29: waiting for node abe2e-2024-10-31-disy-marinerv2gpu to be ready
    pollers.go:57: node abe2e-2024-10-31-disy-marinerv2gpu000000 is ready
    scenario_helpers_test.go:122: node abe2e-2024-10-31-disy-marinerv2gpu is ready, proceeding with validation commands...
    scenario_helpers_test.go:129: 
        	Error Trace:	/mnt/vss/_work/1/s/e2e/scenario_helpers_test.go:129
        	            				/mnt/vss/_work/1/s/e2e/scenario_helpers_test.go:60
        	            				/mnt/vss/_work/1/s/e2e/scenario_test.go:449
        	Error:      	Received unexpected error:
        	            	while running live validator for node abe2e-2024-10-31-disy-marinerv2gpu, unable to get non host debug pod name: failed to find non host debug pod on node abe2e-2024-10-31-disy-marinerv2gpu
        	Test:       	Test_marinerv2gpu
    exec.go:74: executing command on remote VM at 10.224.0.31 of VMSS abe2e-2024-10-31-disy-marinerv2gpu: "cat /var/log/azure/cluster-provision-cse-output.log"
    exec.go:74: executing command on remote VM at 10.224.0.31 of VMSS abe2e-2024-10-31-disy-marinerv2gpu: "sysctl -a"
    exec.go:74: executing command on remote VM at 10.224.0.31 of VMSS abe2e-2024-10-31-disy-marinerv2gpu: "cat /var/log/azure/node-bootstrapper.log"
    exec.go:74: executing command on remote VM at 10.224.0.31 of VMSS abe2e-2024-10-31-disy-marinerv2gpu: "cat /var/log/azure/cluster-provision.log"
I1031 15:47:20.920943  231585 request.go:700] Waited for 3.152942619s due to client-side throttling, not priority and fairness, request: GET:https://abe2e-kubenet-vj1lqils.hcp.westus3.azmk8s.io:443/api/v1/namespaces/default/pods/test-pod-abe2e-2024-10-31-bozi-ubuntu1804chronyrestarts000000
    exec.go:74: executing command on remote VM at 10.224.0.31 of VMSS abe2e-2024-10-31-disy-marinerv2gpu: "journalctl -u kubelet"
    vmss.go:123: vmss "abe2e-2024-10-31-disy-marinerv2gpu" deleted successfully
View more details on Azure Pipelines