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.

Sign up for GitHub

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

Jump to bottom

Fix regression where non-raid attached disks did not determine correct disk type #133

Merged
merged 2 commits into from
Feb 22, 2024
Merged

Fix regression where non-raid attached disks did not determine correct disk type #133

merged 2 commits into from
Feb 22, 2024

Commits on Feb 21, 2024

  1. add unittest for virt ssd hint 

    Add coverage for the diskType hint under kvm

Signed-off-by: Ryan Harper <[email protected]>
    @raharper
    raharper committed Feb 21, 2024
    Configuration menu
    Copy the full SHA
    f0e1e8d View commit details
    Browse the repository at this point in the history

  2. Fix regression where non-raid attached disks did not determine correc… 

    …t disk type

The raid controller merge regressed the path for non-raid attached disks
and all such disks were classified as HDDs.  This was found under KVM
testing where disko uses a prefix in the ID_SERIAL property to set the
disk type to SSD.

Signed-off-by: Ryan Harper <[email protected]>
    @raharper
    raharper committed Feb 21, 2024
    Configuration menu
    Copy the full SHA
    749ccdd View commit details
    Browse the repository at this point in the history