Repository navigation
SslStreamNetworkStreamTest failures "The remote certificate is invalid because of errors in the certificate chain: PartialChain" #112856
Copy link
Copy link
Closed
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarea-System.Net.Securityblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged
Description
Widespread failures on CI
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=960836
Build error leg or test failing:
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "The remote certificate is invalid because of errors in the certificate chain: PartialChain",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=960836
Error message validated: [The remote certificate is invalid because of errors in the certificate chain: PartialChain]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 2/24/2025 12:02:22 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 45 | 45 | 45 |
Metadata
Metadata
Assignees
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarea-System.Net.Securityblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged
Activity
dotnet-policy-service commentedon Feb 24, 2025
Tagging subscribers to this area: @dotnet/ncl, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.
EgorBo commentedon Feb 24, 2025
Looks like it might be #112567 cc @rzikm @wfurt
rzikm commentedon Feb 24, 2025
Yes, interestingly, it did not show in build analysis on the PR, will investigate
wfurt commentedon Feb 24, 2025
I'm wondering if we can restore now session that was created just with certificate...? Or possibly different chain if the certificate was cross-signed (not this case) When the cache was linked to context we did not have that problem.
EgorBo commentedon Feb 24, 2025
I assume it failed only on pipelines which ran on runtime/jit changes only. It looks like it's not the first time (see this) so maybe we should run these pipelines on changes in System Security stuff as well?
rzikm commentedon Feb 24, 2025
The test failed on the PR as well, it just did not show in the Build Analysis. The failure is deterministic and would show on all outerloop pipeline runs.
That is what I found, we need to include all cert(hashes) in the cache key