Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-59654

[RHEl-10] Could not find nvme device in libblockdev nvme_test

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • rhel-10.0
    • libblockdev
    • None
    • No
    • None
    • rhel-sst-storage-management
    • ssg_filesystems_storage_and_HA
    • 4
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None

      What were you trying to do that didn't work?

      What is the impact of this issue to you?

      Please provide the package NVR for which the bug is seen:

      How reproducible is this bug?:

      Steps to reproduce

      1.  
      2.  
      3.  

      Expected results

      Actual results

       

      ======================================================================
      ERROR: test_ns_info (nvme_test.NVMeTestCase.test_ns_info)
      Test namespace info
      ----------------------------------------------------------------------
      Traceback (most recent call last):
        File "/root/rpmbuild/BUILD/libblockdev-3.1.0/tests/nvme_test.py", line 84, in test_ns_info
          info = BlockDev.nvme_get_namespace_info(self.nvme_ns_dev)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      gi.repository.GLib.GError: g-bd-nvme-error-quark: Failed to open device '/dev/nvme0n1': No such file or directory (1) 
      
      ======================================================================
      FAIL: test_format (nvme_test.NVMeTestCase.test_format)
      Test issuing the format command
      ----------------------------------------------------------------------
      gi.repository.GLib.GError: g-bd-nvme-error-quark: Failed to open device '/dev/nvme0n1': No such file or directory (1)During handling of the above exception, another exception occurred:Traceback (most recent call last):
        File "/root/rpmbuild/BUILD/libblockdev-3.1.0/tests/nvme_test.py", line 256, in test_format
          with self.assertRaisesRegex(GLib.GError, message):
      AssertionError: "Couldn't match desired LBA data block size in a device supported LBA format data sizes" does not match "g-bd-nvme-error-quark: Failed to open device '/dev/nvme0n1': No such file or directory (1)"======================================================================
      FAIL: test_sanitize_log (nvme_test.NVMeTestCase.test_sanitize_log)
      Test sanitize log retrieval
      ----------------------------------------------------------------------
      gi.repository.GLib.GError: g-bd-nvme-error-quark: Failed to open device '/dev/nvme0n1': No such file or directory (1)During handling of the above exception, another exception occurred:Traceback (most recent call last):
        File "/root/rpmbuild/BUILD/libblockdev-3.1.0/tests/nvme_test.py", line 280, in test_sanitize_log
          with self.assertRaisesRegex(GLib.GError, message):
      AssertionError: "NVMe Get Log Page - Sanitize Status Log command error: Invalid Field in Command: A reserved coded value or an unsupported value in a defined field|NVMe Get Log Page - Sanitize Status Log command error: unrecognized" does not match "g-bd-nvme-error-quark: Failed to open device '/dev/nvme0n1': No such file or directory (1)"======================================================================
      FAIL: test_self_test (nvme_test.NVMeTestCase.test_self_test)
      Test issuing the self-test command
      ----------------------------------------------------------------------
      gi.repository.GLib.GError: g-bd-nvme-error-quark: Failed to open device '/dev/nvme0n1': No such file or directory (1)During handling of the above exception, another exception occurred:Traceback (most recent call last):
        File "/root/rpmbuild/BUILD/libblockdev-3.1.0/tests/nvme_test.py", line 229, in test_self_test
          with self.assertRaisesRegex(GLib.GError, message):
      AssertionError: "NVMe Device Self-test command error: Invalid Command Opcode: A reserved coded value or an unsupported value in the command opcode field|NVMe Device Self-test command error: Invalid Queue Identifier: The creation of the I/O Completion Queue failed due to an invalid queue identifier specified as part of the command" does not match "g-bd-nvme-error-quark: Failed to open device '/dev/nvme0n1': No such file or directory (1)"----------------------------------------------------------------------
      Ran 429 tests in 3199.465s
      
      Sep 20 00:16:22 dell-r640-072 udisksd[4438]: Error probing device: Error getting Namespace Identifier (NSID): Resource temporarily unavailable (g-bd-nvme-error-quark, 2)
      Sep 20 00:16:34 dell-r640-072 kernel: nvmet: adding nsid 1 to subsystem libblockdev_subnqn
      Sep 20 00:16:34 dell-r640-072 kernel: nvmet: creating nvm controller 1 for subsystem libblockdev_subnqn for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0036-3610-804d-c2c04f5a4333.
      Sep 20 00:16:34 dell-r640-072 kernel: nvme nvme0: creating 64 I/O queues.
      Sep 20 00:16:34 dell-r640-072 kernel: nvme nvme0: new ctrl: "libblockdev_subnqn"
      Sep 20 00:16:34 dell-r640-072 kernel: nvme nvme0: Removing ctrl: NQN "libblockdev_subnqn"
      Sep 20 00:16:34 dell-r640-072 kernel: block nvme0n1: no available path - failing I/O
      Sep 20 00:16:34 dell-r640-072 kernel: block nvme0n1: no available path - failing I/O
      Sep 20 00:16:34 dell-r640-072 kernel: block nvme0n1: no available path - failing I/O
      Sep 20 00:16:34 dell-r640-072 kernel: block nvme0n1: no available path - failing I/O
      Sep 20 00:16:34 dell-r640-072 kernel: block nvme0n1: no available path - failing I/O
      Sep 20 00:16:34 dell-r640-072 kernel: block nvme0n1: no available path - failing I/O
      Sep 20 00:16:34 dell-r640-072 kernel: block nvme0n1: no available path - failing I/O
      Sep 20 00:16:34 dell-r640-072 kernel: block nvme0n1: no available path - failing I/O
      Sep 20 00:16:34 dell-r640-072 kernel: block nvme0n1: no available path - failing I/O
      Sep 20 00:16:34 dell-r640-072 kernel: Buffer I/O error on dev nvme0n1, logical block 262016, async page read
      Sep 20 00:16:34 dell-r640-072 udisksd[4438]: Error probing device: Error getting Namespace Identifier (NSID): Resource temporarily unavailable (g-bd-nvme-error-quark, 2)
      Sep 20 00:16:45 dell-r640-072 kernel: nvmet: adding nsid 1 to subsystem libblockdev_subnqn
      Sep 20 00:16:45 dell-r640-072 kernel: nvmet: creating nvm controller 1 for subsystem libblockdev_subnqn for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0036-3610-804d-c2c04f5a4333.
      Sep 20 00:16:45 dell-r640-072 kernel: nvme nvme0: creating 64 I/O queues.
      Sep 20 00:16:45 dell-r640-072 kernel: nvme nvme0: new ctrl: "libblockdev_subnqn"
      Sep 20 00:16:45 dell-r640-072 kernel: nvme nvme0: Removing ctrl: NQN "libblockdev_subnqn"
      Sep 20 00:16:45 dell-r640-072 kernel: block nvme0n1: no available path - failing I/O
      Sep 20 00:16:45 dell-r640-072 kernel: block nvme0n1: no available path - failing I/O
      Sep 20 00:16:45 dell-r640-072 kernel: Buffer I/O error on dev nvme0n1, logical block 65, async page read
      Sep 20 00:16:45 dell-r640-072 udisksd[4438]: Error probing device: Error getting Namespace Identifier (NSID): Resource temporarily unavailable (g-bd-nvme-error-quark, 2)
      Sep 20 00:17:15 dell-r640-072 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
       

       

       

      libblockdev-3.1.0-7.el10.x86_64

      nvme-cli-2.9.1-4.el10.x86_64

      nvmetcli-0.7-13.el10.noarch

      6.11.0-0.rc5.22.el10.x86_64+debug 

              tbzatek Tomáš Bžatek
              guazhang@redhat.com Guangwu Zhang
              Tomáš Bžatek Tomáš Bžatek
              Guangwu Zhang Guangwu Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: