Installing azure cli is flaky on windows jobs

Question

Installing azure cli is flaky on windows jobs

jsturtevant opened this issue 7 months ago · 5 comments

          vhd failure was

�[0;32m    azure-arm.vhd-windows-2019-containerd:             "summary-line": "Check Azure CLI is installed via alias: exit-status: Error: Command execution timed out (10s)",�[0m

I believe this is a new goss test and may be flaky?

/retest pull-azure-vhds

Originally posted by @jsturtevant in #1353 (comment)

Answer 1 · 2023-12-08T00:16:47.000Z

/sig windows

Answer 2 · 2023-12-08T00:18:40.000Z

@DannyBrito are you seeing any issues on your pipelines?

Answer 3 · 2023-12-08T20:49:32.000Z

@mboersma, have you seen this issue in ADO image builder pipeline?

Answer 4 · 2023-12-08T23:04:31.000Z

I haven't seen this particular error when running the ADO image-builder pipelines, no.

Answer 5 · 2023-12-28T17:54:40.000Z

I'm seeing this often in CI. I think it's more likely that the .MSI was installed by ansible but that the goss test is somehow failing to find it. But honestly I can't tell, and I'm having trouble building Windows locally.

We could maybe trying reverting the goss test to what was originally proposed: #1326 (review)