dotnet dev-certs https --trust failing in on GitHub Actions ubuntu-latest runner in SDK Version 10.0.103

[caleblloyd]

The command dotnet dev-certs https --trust is failing on GitHub Actions ubuntu-latest runners starting with SDK Version 10.0.103

• Example workflow file failing on 10.0.103
• Example run failing on 10.0.103
• Example workflow file working on 10.0.102
• Example run succeeds on 10.0.102

Sample Job:

jobs:
  test:
    name: Tests
    runs-on: ubuntu-latest
    env:
      DOTNET_CLI_TELEMETRY_OPTOUT: 1
      DOTNET_SKIP_FIRST_TIME_EXPERIENCE: 1
    steps:
      - name: Setup dotnet
        uses: actions/setup-dotnet@v5
        with:
          dotnet-version: 10.0.103

      - name: Setup dev certs
        run: dotnet dev-certs https --trust

Failure from 10.0.103:

Run dotnet dev-certs https --trust
[0] ERROR: Exception in Command Processing for EventSource Dotnet-dev-certs: Event WslWindowsTrustSucceeded was assigned event ID 115 but 113 was passed to WriteEvent.
Trusting the HTTPS development certificate was requested. Trust is per-user and may require additional configuration. See https://aka.ms/dev-certs-trust for more information.
There was an error trusting the HTTPS developer certificate. It will be trusted by some clients but not by others.
Error: Process completed with exit code 4.

What I expect (works in 10.0.102):

Run dotnet dev-certs https --trust
Trusting the HTTPS development certificate was requested. Trust is per-user and may require additional configuration. See https://aka.ms/dev-certs-trust for more information.
Successfully trusted the existing HTTPS certificate.

[eerhardt]

Cross posting #65390

Since the fix will need to be in aspnetcore. Looks like a merge error in the release branch:

aspnetcore/src/Shared/CertificateGeneration/CertificateManager.cs

Lines 1322 to 1329 in 3be2a4e

	[Event(115, Level = EventLevel.Verbose, Message = "Successfully trusted the certificate in the Windows certificate store via WSL.")]
	internal void WslWindowsTrustSucceeded() => WriteEvent(113);
	[Event(116, Level = EventLevel.Warning, Message = "Failed to trust the certificate in the Windows certificate store via WSL.")]
	internal void WslWindowsTrustFailed() => WriteEvent(114);
	[Event(117, Level = EventLevel.Warning, Message = "Failed to trust the certificate in the Windows certificate store via WSL: {0}.")]
	internal void WslWindowsTrustException(string exceptionMessage) => WriteEvent(115, exceptionMessage);

These numbers don't align.

cc @danegsta

[danegsta]

There's a PR open to fix the version numbers. Good news is that I think we've got a workaround for GitHub Ubuntu runners (tested on one of ours). Add WSL_INTEROP: "" to the environment variables for your task:

Example:

      - name: Setup dev certs
        run: dotnet dev-certs https --trust
        env:
          WSL_INTEROP: ""

If for some reason this doesn't work on your runner, you can also set continue-on-error: true on the task as certificate trust will have succeeded before that exception was thrown.

[BenLuts]

Running into the same issue on Azure DevOps Pipelines.
ERROR: Exception in Command Processing for EventSource Dotnet-dev-certs: Event WslWindowsTrustSucceeded was assigned event ID 115 but 113 was passed to WriteEvent

[BenLuts]

Can confirm that setting Continue on error to true works.

[danegsta]

dotnet dev-certs https --trust fails with exit code 4 in this scenario (which indicates the certificate is partially trusted) so a more verbose but targeted option if you want CI to fail early when trust fails completely is to compare the exit codes:

- name: Setup dev certs
  run: |
    EXIT_CODE=0
    dotnet dev-certs https --trust || EXIT_CODE=$?
    if [ $EXIT_CODE -ne 0 ] && [ $EXIT_CODE -ne 4 ]; then
      echo "dotnet dev-certs https --trust failed with exit code $EXIT_CODE"
      exit $EXIT_CODE
    fi