-
Notifications
You must be signed in to change notification settings - Fork 132
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
"Manifest generation failed" error in SBOM generation for all build legs #4801
Comments
cc @ViktorHofer - can you please TAL? I think this is a result of dotnet/sdk#45323 |
Thanks for the ping. I believe that the combination of dotnet/sdk#45407 & dotnet/sdk#44969 will fix this. Additionally, dotnet/sdk#45428 will clean this up. |
I know this is fixed so I will pro-actively close the issue. |
Hi @ellahathaway @ViktorHofer , I reopened this issue because the offline legs are still failed with the same issue:
Example build (internal Microsoft link) |
Hmm that doesn't make any sense to me. No idea what's going on here. cc @mmitche in case you have ideas |
Ah it's because it's an offline leg. When running offline builds, we do |
I see, makes sense. Do you have a suggestion on how to handle this? |
Not sure. Maybe there's a way to copy to the files to a new location and direct the SBOM generation to look there? I'm not sure that that would change permissions of the files though. |
If this is about ownership (sudo vs regular user), could we update the owner of the staging folder after the build? |
The Generate SBoM Manifest step from the 1ES templates is failing all build legs (excluding the ones with guardian failures) with the following error:
This step is "succeeding with errors" so it's not failing the overall build. This occurs for 10.0 VMR, but it does not occur in builds of 9.0 and 8.0.
This is likely a regression caused by dotnet/sdk#45323
The text was updated successfully, but these errors were encountered: