RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1733541 - blktests nvme/004 failed
Summary: blktests nvme/004 failed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kernel-rt
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Juri Lelli
QA Contact: Zhang Yi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-26 12:58 UTC by Zhang Yi
Modified: 2022-04-28 01:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-08 02:26:04 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Zhang Yi 2019-07-26 12:58:13 UTC
Description of problem:
blktests nvme/004 failed

Version-Release number of selected component (if applicable):
4.18.0-80.7.1.rt9.153.el8_0.x86_64

How reproducible:
100%

Steps to Reproduce:
1. git clone https://github.com/osandov/blktests.git
1. run blktests ./check nvme/004
2.
3.

Actual results:
Observed this issue with CKI test
https://beaker.engineering.redhat.com/recipes/7167292

From the log, seems the related sysfs was not created

Expected results:


Additional info:

[root@storageqe-31 blktests]# ./check nvme/004
nvme/004 (test nvme and nvmet UUID NS descriptors)           [failed]
    runtime  1.121s  ...  1.114s
    --- tests/nvme/004.out	2019-07-26 07:48:50.409954314 -0400
    +++ /root/tests-beaker/storage/blk/blktests/results/nodev/nvme/004.out.bad	2019-07-26 08:40:36.104265508 -0400
    @@ -1,4 +1,4 @@
     Running nvme/004
    -91fdba0d-f87b-4c25-b80f-db7be1418b9e
    +cat: /sys/block/nvme0n1/uuid: No such file or directory
     uuid.91fdba0d-f87b-4c25-b80f-db7be1418b9e
     Test complete
[root@storageqe-31 blktests]# uname -r
4.18.0-80.7.1.rt9.153.el8_0.x86_64

Comment 9 Zhang Yi 2019-08-08 02:26:04 UTC
The blktests change merged, close this bug.
https://github.com/osandov/blktests/commit/c766fccf3affa426dc1e769ebad755ab093b373d


Note You need to log in before you can comment on or make changes to this bug.