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

Helix failure EPT_S_NOT_REGISTERED #57416

Open
amcasey opened this issue Aug 19, 2024 · 5 comments
Open

Helix failure EPT_S_NOT_REGISTERED #57416

amcasey opened this issue Aug 19, 2024 · 5 comments
Labels
Known Build Error Issue that should show up in Build Analysis test-failure

Comments

@amcasey
Copy link
Member

amcasey commented Aug 19, 2024

We've been seeing a lot of Helix runs fail with a number of messages related to EPT_S_NOT_REGISTERED:

System.ComponentModel.Win32Exception : The Local Security Authority cannot be contacted
System.Security.Cryptography.CryptographicException : There are no more endpoints available from the endpoint mapper.

The failures only occur on Windows and inconsistently affect subsets of the IIS, HTTPS, Data Protection, and Certificate tests.

AFAICT, EPT_S_NOT_REGISTERED indicates that lsass.exe is not available.

Known Issue Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "",
  "ErrorPattern": "(Local Security Authority cannot be contacted)|(no more endpoints available)",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=778691
Error message validated: [(Local Security Authority cannot be contacted)|(no more endpoints available)]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/19/2024 8:44:57 PM UTC

Report

Build Definition Test Pull Request
2571475 dotnet-aspnetcore IIS.ShadowCopy.Tests--net10.0.WorkItemExecution
854997 dotnet/aspnetcore IIS.ShadowCopy.Tests--net10.0.WorkItemExecution
2567252 dotnet-aspnetcore Microsoft.AspNetCore.Server.Kestrel.Sockets.FunctionalTests.Http2.ShutdownTests.GracefulTurnsAbortiveIfRequestsDoNotFinish #44156
2567145 dotnet-aspnetcore Microsoft.AspNetCore.Authentication.Certificate.Test.ClientCertificateAuthenticationTests.VerifyValidSelfSignedWithNoEkuAuthenticates #44156
849273 dotnet/aspnetcore IIS.LongTests--net9.0.WorkItemExecution
849119 dotnet/aspnetcore Interop.FunctionalTests.H2SpecTests.RunIndividualTestCase #58548
2564357 dotnet-aspnetcore IIS.Tests--net10.0.WorkItemExecution
847599 dotnet/aspnetcore IIS.NewShim.FunctionalTests--net8.0.WorkItemExecution
847480 dotnet/aspnetcore Microsoft.AspNetCore.Server.Kestrel.Core.Tests.SniOptionsSelectorTests.FallsBackToHttpsConnectionAdapterCertificate #58466
847326 dotnet/aspnetcore IIS.NewShim.FunctionalTests--net10.0.WorkItemExecution
845573 dotnet/aspnetcore Microsoft.AspNetCore.Server.HttpSys.FunctionalTests--net8.0.WorkItemExecution #58477
845506 dotnet/aspnetcore IIS.LongTests--net9.0.WorkItemExecution
845602 dotnet/aspnetcore Microsoft.AspNetCore.Authentication.Negotiate.NegotiateHandlerFunctionalTests.RequestAfterAuth_ReauthenticatesWhenNotPersisted
845219 dotnet/aspnetcore IIS.LongTests--net10.0.WorkItemExecution #58472
845257 dotnet/aspnetcore Microsoft.AspNetCore.DataProtection.DataProtectionProviderTests.System_UsesProvidedDirectoryAndCertificate #58473
844962 dotnet/aspnetcore IIS.FunctionalTests--net9.0.WorkItemExecution #58462
845081 dotnet/aspnetcore Microsoft.AspNetCore.Server.Kestrel.Sockets.FunctionalTests.Http2.HandshakeTests.TlsAlpnHandshakeSelectsHttp2From1and2 #58464
844955 dotnet/aspnetcore IIS.FunctionalTests--net9.0.WorkItemExecution
843829 dotnet/aspnetcore Microsoft.AspNetCore.Server.Kestrel.Sockets.FunctionalTests.Http2.ShutdownTests.GracefulTurnsAbortiveIfRequestsDoNotFinish #58425
842267 dotnet/aspnetcore Microsoft.AspNetCore.Server.Kestrel.InMemory.FunctionalTests.HttpsConnectionMiddlewareTests.CanReadAndWriteWithHttpsConnectionMiddleware #58428
841975 dotnet/aspnetcore Templates.Mvc.Test.BlazorTemplateTest.BlazorWebTemplate_IndividualAuth
841997 dotnet/aspnetcore Microsoft.AspNetCore.HttpOverrides.CertificateForwardingTests.VerifyHeaderIsUsedIfNoCertificateAlreadySet #58420

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 22
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically label Aug 19, 2024
@amcasey amcasey added test-failure and removed needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically labels Aug 19, 2024
@amcasey amcasey added the Known Build Error Issue that should show up in Build Analysis label Aug 19, 2024
amcasey added a commit to amcasey/aspnetcore that referenced this issue Aug 19, 2024
Supposedly, this will tell us whether the crypto bridge into LSASS is broken.  It may require multiple runs.
@amcasey
Copy link
Member Author

amcasey commented Aug 20, 2024

Possibly relevant: GSA/piv-guides#102 (comment) (via @adityamandaleeka)

@lewing
Copy link
Member

lewing commented Aug 21, 2024

Sdk was is seeing validation errors in windows hosts dotnet/sdk#42870

@lewing
Copy link
Member

lewing commented Aug 21, 2024

did this start with the new helix rollout last week?

@javiercn
Copy link
Member

Merged #57431 that hopefully avoids some of the template test problems.

@radical
Copy link
Member

radical commented Aug 26, 2024

This is the same problem as dotnet/dnceng#3844 AFAICT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Known Build Error Issue that should show up in Build Analysis test-failure
Projects
None yet
Development

No branches or pull requests

4 participants