disk/detect fails and disk-related tests are skipped on eMMC unit

Bug #1522768 reported by Vanessa Chang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox Support Library
Fix Released
Critical
Sylvain Pineau

Bug Description

[Step]
1. Install OS on eMMC unit
2. run disk related tests

[Expected result]
test should be passed

[Actual result]
As OS installed on eMMC unit, the eMMC will be detected as SD card.
The script cannot detect it as a disk, thus the disk/detect fails and the rests of the disk tests cannot be run.

---

[Additional information from Certification team]

a lot of disk tests requires the following:

    device.category == 'DISK'

unfortunately, on computers that don't have a hard disk drive but an eMMC, the category will be 'CARDREADER' and therefore most of the disk/* tests will be skipped.

Related branches

Revision history for this message
Vanessa Chang (vanessa-chang) wrote :

disk/detect

Result: No disk information discovered

Revision history for this message
Pierre Equoy (pieq) wrote :

This issue looks very similar to lp:1458462. Vanessa, do you confirm it's the same kind of issue? If so, I'll mark this one as duplicate.

Also, lp:1458462 has an importance set to "High". Should we raise it to "Critical"?

Revision history for this message
Vanessa Chang (vanessa-chang) wrote :

@Pierre,

They maybe related, but this issue seems more focusing on the Disk detect method.
Here is the log of lsblk

Revision history for this message
Vanessa Chang (vanessa-chang) wrote :
  • disk Edit (442.9 KiB, application/octet-stream)
Pierre Equoy (pieq)
description: updated
Revision history for this message
Pierre Equoy (pieq) wrote :

Regarding the `disk/detect` job, it calls the `disk_info` script which uses `lshw` to retrieve the disks available in the device. If the purpose of this is just to display the disk information in the submission results, maybe we could modify this with `parted -ls`, which returns info from all the storage devices?

As for the rest of the tests, we may have to redefine the udevadm parser in Checkbox support to take into account eMMC drives.

Revision history for this message
Pierre Equoy (pieq) wrote :

Just checked and the `parted -ls` command works on Ubuntu 12.04 and 14.04, so we wouldn't break backward compatibility replaqcing the existing `disk_info` script.

summary: - disk_detect fails on eMMC unit
+ disk/detect fails and disk-related tests are skipped on eMMC unit
Revision history for this message
Pierre Equoy (pieq) wrote :

<vanessachang1> ePierre: in OSP1, only disk/detect, disk/read_performance and disk/smart are cert-blocker

→ I will focus on having these 3 tests available for devices with eMMC/NVMe devices.

Revision history for this message
Pierre Equoy (pieq) wrote :

Attached is the feedback provided by the udev_resource script used to parse the content of the udevadm database on the device Vanessa tested.

I suppose the eMMC drive is the following:

path: /devices/platform/MSFT0101:00
bus: platform
vendor: M-Systems Flash Disk Pioneers

Given the fact that there is no `driver` section, the current version of our parser does not even provide a `category` field for it! Moreover, the `path` cannot be used for the disk/read_performance_* tests...

Revision history for this message
Pierre Equoy (pieq) wrote :
Changed in plainbox-provider-checkbox:
assignee: nobody → Sylvain Pineau (sylvain-pineau)
status: Confirmed → In Progress
Revision history for this message
Pierre Equoy (pieq) wrote :

In some devices, both traditional HDD and more recent eMMC or NVMe drives can be found.

For instance attached is the output of `udevadm info --export-db` from a device with both a 500 GB hard disk and a 256 GB NVMe drive.

For information, on this device, the NVMe drive is mounted as / and the HDD is mounted as `/media/...`.

affects: plainbox-provider-checkbox → checkbox-support
Changed in checkbox-support:
milestone: none → 0.24
Changed in checkbox-support:
status: In Progress → Fix Committed
Pierre Equoy (pieq)
Changed in checkbox-support:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.