Skip to content

Conversation

@LakshmiSaiHarika
Copy link
Contributor

  • This pull request resolves the beacon report issue caused by the absence of the VERSION_ID field in the /etc/os-release file on Debian forky distribution.
  • Additionally, this pull request introduces a pre-release tag for any development-stage Linux distribution that lacks a VERSION_ID in its /etc/os-release file.
image

Debian Forky SNP certification GH Issue link: here

@LakshmiSaiHarika LakshmiSaiHarika force-pushed the beacon-report-fix-for-debian-forky branch from edbbf6a to 32b21ad Compare November 3, 2025 04:39
Copy link
Contributor

@DGonzalezVillal DGonzalezVillal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I say remove the pre-release milestone thing. Just certify the rolling release versions to the sev-certify version that it passes. The version-id change works well although.


# Call beacon
if [ -e "${SEV_CERT_FILE}" ] && [ -z "$(grep "" "${SEV_CERT_FILE}")" ] && [ "${SET_MILESTONE}" == "true" ]; then
if [ -e "${SEV_CERT_FILE}" ] && [ -z "$(grep "" "${SEV_CERT_FILE}")" ] && [ "${SET_MILESTONE}" == "true" ] && [ "${OS_PRE_RELEASE}" == "true" ]; then
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The milestones are being used to tell us what sev-certify version the OS is certified in. so this pre-release milestone is confusing. I think it's fine if we just put the rolling release with the other official release. IT's technically not a "pre-release".

VERSION_ID environment variable is not present in /etc/os-release file
in the Debian forky release.

Signed-off-by: Harika Nittala <[email protected]>
@LakshmiSaiHarika LakshmiSaiHarika force-pushed the beacon-report-fix-for-debian-forky branch from 32b21ad to 067e214 Compare November 5, 2025 22:20
@DGonzalezVillal DGonzalezVillal merged commit 2a42984 into AMDEPYC:main Nov 5, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants