NuGet failing with Response status code does not indicate success: 503 (Service Unavailable)

[jkotas]

Build

https://dev.azure.com/dnceng-public/public/_build/results?buildId=300923&view=results

Build leg reported

Build / Installer Build and Test coreclr windows_x86 Debug / Build

Pull Request

https://github.com/dotnet/runtime/pull/78801

Action required for the engineering services team

To triage this issue (First Responder / @dotnet/dnceng):

• [ ] Open the failing build above and investigate
• [ ] Add a comment explaining your findings

If this is an issue that is causing build breaks across multiple builds and would get benefit from being listed on the build analysis check, follow the next steps:

1. Add the label "Known Build Error"
2. Edit this issue and add an error string in the Json below that can help us match this issue with future build breaks. You should use the known issues documentation

{
   "ErrorMessage" : "Failed to retrieve information about",
   "BuildRetry": true
}

Release Note Category

• [ ] Feature changes/additions
• [ ] Bug fixes
• [ ] Internal Infrastructure Improvements

Release Note Description

Additional information about the issue reported

No response

Report

Build	Definition	Step Name	Console log	Pull Request
2732285	dotnet-sdk	Build	Log	#50939
2732118	dotnet-sdk	Build	Log
2731748	dotnet-sdk	Build	Log	#50943
2730296	dotnet-sdk	Build	Log
2729822	dotnet-sdk	Build	Log
2729775	dotnet-sdk	Build	Log
2729774	dotnet-sdk	Build	Log
2729236	dotnet-sdk	Build	Log	#50854
2728913	dotnet-sdk	Build (cblMariner20Fpm)	Log
2728916	dotnet-sdk	Build	Log	#50126
2728921	dotnet-sdk	Build	Log	#50829
2728427	dotnet-sdk	Build	Log	#50639
1065084	dotnet/aspnetcore	Build ARM64	Log	dotnet/aspnetcore#62286
2727908	dotnet-sdk	Build	Log	#50782
2727797	dotnet-sdk	Build	Log
2727796	dotnet-sdk	Build	Log
2727540	dotnet-sdk	Build	Log	#50199
2727480	dotnet-sdk	Build	Log
2727395	dotnet-sdk	Build	Log
1063322	dotnet/runtime	Build product	Log
2726723	dotnet-sdk	Build	Log	#50639
2726631	dotnet-sdk	Build	Log	#50639
1062599	dotnet/runtime	Send tests to Helix (Windows)	Log	dotnet/runtime#115566
1062503	dotnet/aspnetcore	Build shared fx	Log	dotnet/aspnetcore#62112
2726180	dotnet-aspnetcore	Build shared fx	Log
2726104	dotnet-sdk	Build	Log
2724388	dotnet-sdk	Build	Log
1059334	dotnet/runtime	Build product	Log	dotnet/runtime#116082
1059330	dotnet/roslyn	Build Bootstrap Compiler	Log	dotnet/roslyn#78685
1059339	dotnet/sdk	Build	Log	dotnet/sdk#49072
1059331	dotnet/sdk	Build	Log	dotnet/sdk#49061
2723286	dotnet-sdk	Build (debian12Amd64)	Log	#50639
2723288	dotnet-sdk	Build	Log	#50201
2723224	dotnet-sdk	Build	Log
1059013	dotnet/aspnetcore	Build shared fx	Log	dotnet/aspnetcore#62222
2722213	dotnet-runtime	Build product	Log
2721779	dotnet-roslyn	Build - Validate Correctness	Log
1057101	dotnet/runtime	Build product	Log
2720265	dotnet-performance	Run performance job script	Log
1054985	dotnet/runtime	Build product	Log	dotnet/runtime#116136
1054128	dotnet/runtime	Send tests to Helix (Windows)	Log	dotnet/runtime#116081
2718054	dotnet-sdk	Build	Log
1050603	dotnet/aspire	Build	Log	dotnet/aspire#9503
1050602	dotnet/aspire	Build	Log	dotnet/aspire#9503
2715230	dotnet-sdk	Build	Log	#50353
2715169	dotnet-performance	Run performance job script	Log

Build	Definition	Test	Pull Request
1064204	dotnet/roslyn	Microsoft.CodeAnalysis.MSBuild.UnitTests.NewlyCreatedProjectsFromDotNetNew.ValidateCSharpTemplateProjects	dotnet/roslyn#78905
2726588	dotnet-roslyn	Microsoft.CodeAnalysis.MSBuild.UnitTests.NewlyCreatedProjectsFromDotNetNew.ValidateCSharpTemplateProjects
2725812	dotnet-roslyn	workitem_262.WorkItemExecution
1050594	dotnet/runtime	Workloads-ST-Wasm.Build.NativeRebuild.Tests.FlagsChangeRebuildTests.WorkItemExecution
2716251	dotnet-roslyn	Microsoft.CodeAnalysis.MSBuild.UnitTests.NewlyCreatedProjectsFromDotNetNew.ValidateVisualBasicTemplateProjects

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	4	51

Known issue validation

Build: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=300923 Result validation: :white_check_mark: Known issue matched with the provided build.

[andriipatsula]

Updated an ErrorMessage

[jkotas]

Updated an ErrorMessage

This error message is too specific. The package name does not matter for 503 errors. You can see it in the log file attached to this issue. The build failure was caused by multiple different packages failing to be retrieved - for example, look for Failed to retrieve information about 'Microsoft.Build.Tasks.Git'.

[andriipatsula]

Yeh, most probably Failed to retrieve information about pattern should work.

[ulisesh]

15 hits in the last 24 hours, I'm going to enable build retry

[MattGal]

Created IcM to ask for investigation here as well, https://portal.microsofticm.com/imp/v3/incidents/details/353857134/home

[ulisesh]

More hits today.

Update from the IcM: "Will check throttling limits to see if that's kicking in here"

[epananth]

I updated the ICM and received no response from them.

[dougbu]

Where are 500s from the public AzDO feeds tracked❔ I don't see efcore-ci build #20230213.2 mentioned here for example. That build matches the ErrorMessage in the description above.

[ulisesh]

Does the EFCore repo uses build analysis? Known issues tracking is part of build analysis

[dougbu]

Might need a separate Known Build Error for the dotnet-public-npm feed errors we're seeing in dotnet/aspnetcore (a lot). For example,

  error An unexpected error occurred: "https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public-npm/npm/registry/istanbul-lib-report/-/istanbul-lib-report-3.0.0.tgz: Request failed \"500 Internal Server Error\"".
  info If you think this is a bug, please open a bug report with the information provided in "/Users/runner/work/1/s/src/SignalR/clients/ts/common/yarn-error.log".
  info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
  Process stalled
  Active handles:
    - Socket
    - Socket
    - Socket
    - TLSSocket
    - TLSSocket
    - TLSSocket
    - TLSSocket
    - TLSSocket
/Users/runner/work/1/s/eng/targets/Npm.Common.targets(45,5): error MSB6006: "yarn" exited with code 1. [/Users/runner/work/1/s/src/SignalR/clients/ts/common/common.npmproj]
##[error]eng/targets/Npm.Common.targets(45,5): error MSB6006: (NETCORE_ENGINEERING_TELEMETRY=Restore) "yarn" exited with code 1.

Affected aspnetcore-ci rolling builds over the last week:

• #20230211.3
• #20230212.5
• #20230213.40
• #20230214.6

[dougbu]

Does the EFCore repo uses build analysis? Known issues tracking is part of build analysis

No.

/cc @bricelam and @ajcvickers because I don't remember why they didn't opt in and don't know if those reasons remain valid.

[MattGal]

@dougbu this one's on me, the NPM failures you're talking about are https://github.com/dotnet/arcade/issues/11737. While the IcM for it is unanswered, the known issues system said no repros for a week so I had closed it. Feel free to reactivate. It won't make Azure Devops any more responsive, but it will keep it on our radar.

[dougbu]

Would that issue have picked up the efcore-ci failure given it occurred in a rolling build (where build analysis isn't relevant) for a repo where build analysis isn't enabled anyhow❔

[dougbu]

In any case, the ErrorMessage above means this issue will capture a superset of those tracked in #11737. I'll reopen the other one just because 500 and 503 aren't the same number :grin:

[dougbu]

Oh, ignore my last comment. You were talking about the dotnet-public-npm failures. Right @MattGal❔

[dougbu]

Side note: The Known Build Errors infrastructure is tilted pretty far toward PR failures. It's far too manual (AFAICT) to use for rolling build failures and the https://msit.powerbi.com/groups/de8c4cb8-b06d-4af8-8609-3182bb4bdc7c/reports/f0702582-7c04-47ca-a145-6ac37fd25813/ReportSectioncb62e8e5baebca8883e1?experience=power-bi doesn't seem to automatically report matches for such issues (nor help enough in creating them).

[MattGal]

Oh, ignore my last comment. You were talking about the dotnet-public-npm failures. Right @MattGal❔

Correct I was keying off you talking about "pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public-npm/npm/registry/istanbul-lib-report/-/istanbul-lib-report-3.0.0.tgz" since that's not nuget-y

[markwilkie]

Side note: The Known Build Errors infrastructure is tilted pretty far toward PR failures. It's far too manual (AFAICT) to use for rolling build failures and the https://msit.powerbi.com/groups/de8c4cb8-b06d-4af8-8609-3182bb4bdc7c/reports/f0702582-7c04-47ca-a145-6ac37fd25813/ReportSectioncb62e8e5baebca8883e1?experience=power-bi doesn't seem to automatically report matches for such issues (nor help enough in creating them).

@AlitzelMendez - any feedback here?

[epananth]

@ilyas1974 assigning this to you, cos you were looking at a similar issue

[AlitzelMendez]

Side note: The Known Build Errors infrastructure is tilted pretty far toward PR failures. It's far too manual (AFAICT) to use for rolling build failures and the https://msit.powerbi.com/groups/de8c4cb8-b06d-4af8-8609-3182bb4bdc7c/reports/f0702582-7c04-47ca-a145-6ac37fd25813/ReportSectioncb62e8e5baebca8883e1?experience=power-bi doesn't seem to automatically report matches for such issues (nor help enough in creating them).

@AlitzelMendez - any feedback here?

so after some months I saw this comment :) I think we explored this option in the past but I never found the dashboard in which we wanted to add a link to create known issue, but I think is a great and reasonable idea. reopening: https://github.com/dotnet/arcade/issues/8794