Skip to content

[AUTOPATCHER-kernel] Kernel upgrade to version 6.6.96.2 - branch 3.0-dev #14525

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

Open
wants to merge 1 commit into
base: 3.0-dev
Choose a base branch
from

Conversation

CBL-Mariner-Bot
Copy link
Collaborator

[AUTOPATCHER-kernel] Kernel upgrade to version 6.6.96.2 - branch 3.0-dev
Upgrade pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=900835&view=results

buddy build -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=900852&view=results

@CBL-Mariner-Bot
Copy link
Collaborator Author

🚨 PR Check Failed - Critical Issues Found

Found 3 critical/error issue(s) that must be fixed.

🔍 Critical Issues Detected:

  1. Missing Patch File (ERROR)
    • Patch file '0001-add-mstflint-kernel-%{mstflintver}.patch' is referenced in the spec but not found in the directory
    • 💡 Fix: Add the missing patch file or update the Patch reference
  2. Missing Patch File (ERROR)
    • Patch file '0001-add-mstflint-kernel-%{mstflintver}.patch' is referenced in the spec but not found in the directory
    • 💡 Fix: Add the missing patch file or update the Patch reference
  3. Missing Patch File (ERROR)
    • Patch file '0001-add-mstflint-kernel-%{mstflintver}.patch' is referenced in the spec but not found in the directory
    • 💡 Fix: Add the missing patch file or update the Patch reference

🤖 AI Analysis Summary:

Brief Analysis: The update bumps the kernel version from 6.6.96.1 to 6.6.96.2 in multiple spec files and associated metadata; the single patch (for mstflint) is referenced using a macro and is present in the package directory.
Critical Issues Found: No ERROR/CRITICAL security issues detected – all referenced patches follow the proper naming and are applied through the autosetup mechanism.
Recommended Actions:
• Confirm that any CVE fixes already documented in previous changelog entries remain valid and that no new CVE updates are needed.
• Continue using consistent patch numbering and %autosetup usage.
• Double-check that security‐related BuildRequires (e.g. audit-devel, openssl, etc.) remain current for ongoing hardening.


📋 For detailed analysis and recommendations, check the Azure DevOps pipeline logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.0-dev PRs Destined for AzureLinux 3.0 Automatic PR AutoUpgrade Kernel Packaging specs-extended PR to fix SPECS-EXTENDED Tools
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant