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

"Manifest generation failed" error in SBOM generation for all build legs #4801

Closed
ellahathaway opened this issue Dec 10, 2024 · 9 comments · Fixed by dotnet/sdk#45489
Closed
Labels
area-build Improvements in source-build's own build process ops-monitor Issues created/handled by the source build monitor role untriaged

Comments

@ellahathaway
Copy link
Member

The Generate SBoM Manifest step from the 1ES templates is failing all build legs (excluding the ones with guardian failures) with the following error:

##[error]Encountered an error while generating the manifest.
##[error]Error details: Access to the path '/mnt/vss/_work/1/s/artifacts/staging/_manifest' is denied.

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

@ellahathaway ellahathaway added the ops-monitor Issues created/handled by the source build monitor role label Dec 10, 2024
@dotnet-issue-labeler dotnet-issue-labeler bot added area-build Improvements in source-build's own build process untriaged labels Dec 10, 2024
@ellahathaway
Copy link
Member Author

cc @ViktorHofer - can you please TAL? I think this is a result of dotnet/sdk#45323

@ViktorHofer
Copy link
Member

ViktorHofer commented Dec 12, 2024

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.

@ViktorHofer
Copy link
Member

I know this is fixed so I will pro-actively close the issue.

@github-project-automation github-project-automation bot moved this from Backlog to Done in .NET Source Build Dec 12, 2024
@Winniexu01
Copy link
Member

Hi @ellahathaway @ViktorHofer , I reopened this issue because the offline legs are still failed with the same issue:

##[error]Encountered an error while generating the manifest.
##[error]Error details: Access to the path '/__w/1/a/artifacts/_manifest' is denied.

Example build (internal Microsoft link)

@Winniexu01 Winniexu01 reopened this Dec 13, 2024
@ViktorHofer
Copy link
Member

Hmm that doesn't make any sense to me. No idea what's going on here. cc @mmitche in case you have ideas

@ellahathaway
Copy link
Member Author

ellahathaway commented Dec 16, 2024

Ah it's because it's an offline leg. When running offline builds, we do sudo unshare -n. This makes the files produced by the build only accessible by commands run with administrator privileges. sudo is necessary here to unshare the network, otherwise I'd suggest that we just remove it

@ViktorHofer
Copy link
Member

ViktorHofer commented Dec 16, 2024

I see, makes sense. Do you have a suggestion on how to handle this?

@ellahathaway
Copy link
Member Author

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.

@ViktorHofer
Copy link
Member

If this is about ownership (sudo vs regular user), could we update the owner of the staging folder after the build?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-build Improvements in source-build's own build process ops-monitor Issues created/handled by the source build monitor role untriaged
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants