-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Signature thumbprint do not match expected #9188
Comments
Hello @philcart . Thanks for your report. We will merge fix as as possible. |
Should be fixed in |
Hi guys, And in the context of CD concepts , this is kind of problematic. Regards, |
I can confirm that I've hit this issue again today:
I would like to reiterate the above comment requesting a longer term solution for this rather than a manual update. |
I'm experiencing the same problem and I've updated the signature for VS. #9502 |
I would also like to see a long term solution to signatures not matching issue. This happens too often and wastes a lot of time. It is really annoying to wait 2-3 hours for a build and to see that it failed because the signature of a single tool has changed. |
we are having a similar issue for AzureCLI from few days. 2024-05-02T21:04:29.1761743Z ==> azure-arm.image: Provisioning with powershell script: /agent/_work/3/s/runner-images/images/windows/templates/../scripts/build/Install-AzureCli.ps1 Can you please upgrade the signature and let me know. Thank you, |
Description
==> azure-arm.image: Waiting for machine to restart...
==> azure-arm.image: A system shutdown is in progress.(1115)
azure-arm.image: pkrvms4osbkppd6 restarted.
==> azure-arm.image: #< CLIXML
==> azure-arm.image: System.Management.Automation.PSCustomObjectSystem.Object1Preparing modules for first use.0-1-1Completed-1 1Preparing modules for first use.0-1-1Completed-1
==> azure-arm.image: Machine successfully restarted, moving on
==> azure-arm.image: Provisioning with Powershell...
==> azure-arm.image: Provisioning with powershell script: C:/Dev/runner-images/images/windows/templates/../scripts/build/Install-VisualStudio.ps1
azure-arm.image: Downloading Bootstrapper ...
azure-arm.image: Downloading package from https://aka.ms/vs/17/release/vs_Enterprise.exe to C:\Users\INSTAL~1\AppData\Local\Temp\vs_Enterprise.exe...
azure-arm.image: Package downloaded in 1 seconds
azure-arm.image: Signature thumbprint do not match expected.
azure-arm.image: At C:\Program Files\WindowsPowerShell\Modules\ImageHelpers\InstallHelpers.ps1:972 char:9
azure-arm.image: + throw "Signature thumbprint do not match expected."
azure-arm.image: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
azure-arm.image: + CategoryInfo : OperationStopped: (Signature thumb...match expected.:String) [], RuntimeException
azure-arm.image: + FullyQualifiedErrorId : Signature thumbprint do not match expected.
azure-arm.image:
==> azure-arm.image: Script exited with non-zero exit status: 1. Allowed exit codes are: [0 3010]
==> azure-arm.image: Step "StepProvision" failed
==> azure-arm.image: [c] Clean up and exit, [a] abort without cleanup, or [r] retry step (build may fail even if retry succeeds)?
Platforms affected
Runner images affected
Image version and build link
main branch cloned at
192a94d
Is it regression?
N/A
Expected behavior
New Windows2022 runner image built
Actual behavior
Errors with the above message
Repro steps
The text was updated successfully, but these errors were encountered: