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.

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

Add release notes for security patch 20241031T000000Z #5190

Closed
wants to merge 4 commits into from

Add release notes for security patch 20241031T000000Z

a3aa90c
Select commit
Loading
Failed to load commit list.
Closed

Add release notes for security patch 20241031T000000Z #5190

Add release notes for security patch 20241031T000000Z
a3aa90c
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Agentbaker E2E failed Oct 31, 2024 in 37m 47s

Build #20241031.16 had test failures

Details

Tests

  • Failed: 5 (9.62%)
  • Passed: 47 (90.38%)
  • Other: 0 (0.00%)
  • Total: 52

Annotations

Check failure on line 2969 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Build log #L2969

Bash exited with code '1'.

Check failure on line 1 in Test_azurelinuxv2ARM64

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Test_azurelinuxv2ARM64

Failed
Raw output
    vhd.go:230: image version /subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/AzureLinuxV2gen2arm64/versions/1.1730361893.10265 is already replicated to region westus3
    scenario_helpers_test.go:96: running scenario "Test_azurelinuxv2ARM64" with vhd: "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/AzureLinuxV2gen2arm64/versions/1.1730361893.10265", tags {Name:Test_azurelinuxv2ARM64 ImageName:AzureLinuxV2gen2arm64 OS:azurelinux Arch:arm64 Airgap:false GPU:false WASM:false ServerTLSBootstrapping:false Scriptless:false}
    scenario_helpers_test.go:102: running scenario "Test_azurelinuxv2ARM64" with image "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/AzureLinuxV2gen2arm64/versions/1.1730361893.10265" 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-8z4g-azurelinuxv2arm64" in resource group "MC_abe2e-westus3_abe2e-kubenet-331fc_westus3"
    scenario_helpers_test.go:110: vmss abe2e-2024-10-31-8z4g-azurelinuxv2arm64 creation succeeded, proceeding with node readiness and pod checks...
    pollers.go:29: waiting for node abe2e-2024-10-31-8z4g-azurelinuxv2arm64 to be ready
    pollers.go:57: node abe2e-2024-10-31-8z4g-azurelinuxv2arm64000000 is ready
    scenario_helpers_test.go:122: node abe2e-2024-10-31-8z4g-azurelinuxv2arm64 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:68
        	Error:      	Received unexpected error:
        	            	while running live validator for node abe2e-2024-10-31-8z4g-azurelinuxv2arm64, unable to get non host debug pod name: failed to find non host debug pod on node abe2e-2024-10-31-8z4g-azurelinuxv2arm64
        	Test:       	Test_azurelinuxv2ARM64
    exec.go:74: executing command on remote VM at 10.224.0.36 of VMSS abe2e-2024-10-31-8z4g-azurelinuxv2arm64: "cat /var/log/azure/node-bootstrapper.log"
    exec.go:74: executing command on remote VM at 10.224.0.36 of VMSS abe2e-2024-10-31-8z4g-azurelinuxv2arm64: "cat /var/log/azure/cluster-provision.log"
    exec.go:74: executing command on remote VM at 10.224.0.36 of VMSS abe2e-2024-10-31-8z4g-azurelinuxv2arm64: "journalctl -u kubelet"
I1031 18:09:57.918338   71753 request.go:700] Waited for 1.317599368s due to client-side throttling, not priority and fairness, request: GET:https://abe2e-kubenet-o9b61kuu.hcp.westus3.azmk8s.io:443/api/v1/namespaces/default/pods/test-pod-abe2e-2024-10-31-xrnl-azurelinuxv2messageoftheday000000
    exec.go:74: executing command on remote VM at 10.224.0.36 of VMSS abe2e-2024-10-31-8z4g-azurelinuxv2arm64: "cat /var/log/azure/cluster-provision-cse-output.log"
    exec.go:74: executing command on remote VM at 10.224.0.36 of VMSS abe2e-2024-10-31-8z4g-azurelinuxv2arm64: "sysctl -a"
    vmss.go:123: vmss "abe2e-2024-10-31-8z4g-azurelinuxv2arm64" deleted successfully

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-rouc-azurelinuxv2chronyrestarts" in resource group "MC_abe2e-westus3_abe2e-kubenet-331fc_westus3"
    scenario_helpers_test.go:110: vmss abe2e-2024-10-31-rouc-azurelinuxv2chronyrestarts creation succeeded, proceeding with node readiness and pod checks...
    pollers.go:29: waiting for node abe2e-2024-10-31-rouc-azurelinuxv2chronyrestarts to be ready
    pollers.go:57: node abe2e-2024-10-31-rouc-azurelinuxv2chronyrestarts000000 is ready
    scenario_helpers_test.go:122: node abe2e-2024-10-31-rouc-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-rouc-azurelinuxv2chronyrestarts, unable to get non host debug pod name: failed to find non host debug pod on node abe2e-2024-10-31-rouc-azurelinuxv2chronyrestarts
        	Test:       	Test_azurelinuxv2ChronyRestarts
    exec.go:74: executing command on remote VM at 10.224.0.40 of VMSS abe2e-2024-10-31-rouc-azurelinuxv2chronyrestarts: "cat /var/log/azure/cluster-provision.log"
    exec.go:74: executing command on remote VM at 10.224.0.40 of VMSS abe2e-2024-10-31-rouc-azurelinuxv2chronyrestarts: "journalctl -u kubelet"
    exec.go:74: executing command on remote VM at 10.224.0.40 of VMSS abe2e-2024-10-31-rouc-azurelinuxv2chronyrestarts: "cat /var/log/azure/cluster-provision-cse-output.log"
    exec.go:74: executing command on remote VM at 10.224.0.40 of VMSS abe2e-2024-10-31-rouc-azurelinuxv2chronyrestarts: "sysctl -a"
    exec.go:74: executing command on remote VM at 10.224.0.40 of VMSS abe2e-2024-10-31-rouc-azurelinuxv2chronyrestarts: "cat /var/log/azure/node-bootstrapper.log"
    vmss.go:123: vmss "abe2e-2024-10-31-rouc-azurelinuxv2chronyrestarts" deleted successfully

Check failure on line 1 in Test_marinerv2CustomSysctls

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Test_marinerv2CustomSysctls

Failed
Raw output
    scenario_helpers_test.go:96: running scenario "Test_marinerv2CustomSysctls" with vhd: "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/CBLMarinerV2gen2/versions/1.1730362027.21434", tags {Name:Test_marinerv2CustomSysctls ImageName:CBLMarinerV2gen2 OS:mariner Arch:amd64 Airgap:false GPU:false WASM:false ServerTLSBootstrapping:false Scriptless:false}
    scenario_helpers_test.go:102: running scenario "Test_marinerv2CustomSysctls" 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-8ech-marinerv2customsysctls" in resource group "MC_abe2e-westus3_abe2e-kubenet-331fc_westus3"
    scenario_helpers_test.go:110: vmss abe2e-2024-10-31-8ech-marinerv2customsysctls creation succeeded, proceeding with node readiness and pod checks...
    pollers.go:29: waiting for node abe2e-2024-10-31-8ech-marinerv2customsysctls to be ready
    pollers.go:57: node abe2e-2024-10-31-8ech-marinerv2customsysctls000000 is ready
    scenario_helpers_test.go:122: node abe2e-2024-10-31-8ech-marinerv2customsysctls 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:416
        	Error:      	Received unexpected error:
        	            	while running live validator for node abe2e-2024-10-31-8ech-marinerv2customsysctls, unable to get non host debug pod name: failed to find non host debug pod on node abe2e-2024-10-31-8ech-marinerv2customsysctls
        	Test:       	Test_marinerv2CustomSysctls
    exec.go:74: executing command on remote VM at 10.224.0.38 of VMSS abe2e-2024-10-31-8ech-marinerv2customsysctls: "cat /var/log/azure/cluster-provision.log"
    exec.go:74: executing command on remote VM at 10.224.0.38 of VMSS abe2e-2024-10-31-8ech-marinerv2customsysctls: "journalctl -u kubelet"
    exec.go:74: executing command on remote VM at 10.224.0.38 of VMSS abe2e-2024-10-31-8ech-marinerv2customsysctls: "cat /var/log/azure/cluster-provision-cse-output.log"
    exec.go:74: executing command on remote VM at 10.224.0.38 of VMSS abe2e-2024-10-31-8ech-marinerv2customsysctls: "sysctl -a"
    exec.go:74: executing command on remote VM at 10.224.0.38 of VMSS abe2e-2024-10-31-8ech-marinerv2customsysctls: "cat /var/log/azure/node-bootstrapper.log"
    vmss.go:123: vmss "abe2e-2024-10-31-8ech-marinerv2customsysctls" deleted successfully

Check failure on line 1 in Test_marinerv2Wasm

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Test_marinerv2Wasm

Failed
Raw output
    vhd.go:230: image version /subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/CBLMarinerV2gen2/versions/1.1730362027.21434 is already replicated to region westus3
    scenario_helpers_test.go:96: running scenario "Test_marinerv2Wasm" with vhd: "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/CBLMarinerV2gen2/versions/1.1730362027.21434", tags {Name:Test_marinerv2Wasm ImageName:CBLMarinerV2gen2 OS:mariner Arch:amd64 Airgap:false GPU:false WASM:true ServerTLSBootstrapping:false Scriptless:false}
    scenario_helpers_test.go:102: running scenario "Test_marinerv2Wasm" 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-j0n6-marinerv2wasm" in resource group "MC_abe2e-westus3_abe2e-kubenet-331fc_westus3"
    scenario_helpers_test.go:110: vmss abe2e-2024-10-31-j0n6-marinerv2wasm creation succeeded, proceeding with node readiness and pod checks...
    pollers.go:29: waiting for node abe2e-2024-10-31-j0n6-marinerv2wasm to be ready
    pollers.go:57: node abe2e-2024-10-31-j0n6-marinerv2wasm000000 is ready
    validation.go:24: wasm scenario: running wasm validation on abe2e-2024-10-31-j0n6-marinerv2wasm000000...
    scenario_helpers_test.go:122: node abe2e-2024-10-31-j0n6-marinerv2wasm 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:501
        	Error:      	Received unexpected error:
        	            	while running live validator for node abe2e-2024-10-31-j0n6-marinerv2wasm, unable to get non host debug pod name: failed to find non host debug pod on node abe2e-2024-10-31-j0n6-marinerv2wasm
        	Test:       	Test_marinerv2Wasm
    exec.go:74: executing command on remote VM at 10.224.0.6 of VMSS abe2e-2024-10-31-j0n6-marinerv2wasm: "cat /var/log/azure/cluster-provision.log"
    exec.go:74: executing command on remote VM at 10.224.0.6 of VMSS abe2e-2024-10-31-j0n6-marinerv2wasm: "journalctl -u kubelet"
    exec.go:74: executing command on remote VM at 10.224.0.6 of VMSS abe2e-2024-10-31-j0n6-marinerv2wasm: "cat /var/log/azure/cluster-provision-cse-output.log"
    exec.go:74: executing command on remote VM at 10.224.0.6 of VMSS abe2e-2024-10-31-j0n6-marinerv2wasm: "sysctl -a"
    exec.go:74: executing command on remote VM at 10.224.0.6 of VMSS abe2e-2024-10-31-j0n6-marinerv2wasm: "cat /var/log/azure/node-bootstrapper.log"
    vmss.go:123: vmss "abe2e-2024-10-31-j0n6-marinerv2wasm" deleted successfully