-
Notifications
You must be signed in to change notification settings - Fork 810
Closed
Labels
#g-security-complianceSecurity & Compliance product groupSecurity & Compliance product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.Ready to write code. Scheduled in a release. See "Making changes" in handbook.bugSomething isn't working as documentedSomething isn't working as documented~assisting qaThis issue can be QA'd by anyone outside the QA team when capacity allowsThis issue can be QA'd by anyone outside the QA team when capacity allows
Milestone
Description
Fleet version: 4.80.1
Web browser and operating system: N/A
💥 Actual behavior
Dogfood: https://dogfood.fleetdm.com/software/os/153
🛠️ To fix
See below. Only software.name = kernel should get marked as isKernel
🧑💻 Steps to reproduce
These steps:
- Have been confirmed to consistently lead to reproduction in multiple Fleet instances.
- Describe the workflow that led to the error, but have not yet been reproduced in multiple Fleet instances.
- Enroll RHEL based host (Alma)
- Refetch host
- run cleanups_then_aggregation cron
- run vulnerabilities cron
- navigate to Software > OS > Alma
🕯️ More info (optional)
Software ingestion is marking both package names "kernel" and "kernel-core" as isKernel in Fleet. These both refer to the same kernel on RHEL.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
#g-security-complianceSecurity & Compliance product groupSecurity & Compliance product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.Ready to write code. Scheduled in a release. See "Making changes" in handbook.bugSomething isn't working as documentedSomething isn't working as documented~assisting qaThis issue can be QA'd by anyone outside the QA team when capacity allowsThis issue can be QA'd by anyone outside the QA team when capacity allows
Type
Projects
Status
Done
