yahoo-eng-team team mailing list archive

[OpenStack Infra <1792313@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/602351
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a1325b4c76ba5ad42a09370d6250338cfb3de533
Submitter: Zuul
Branch:    master

commit a1325b4c76ba5ad42a09370d6250338cfb3de533
Author: Hamdy Khader <hamdyk@xxxxxxxxxxxx>
Date:   Thu Sep 13 16:24:54 2018 +0300

    Set defult value of num_nvme_discover_tries=5
    
    Discovering newly connected devices in the initiator side can be slow
    when there are old connections, increasing the retries is important
    to discover the new connected device.
    
    Change-Id: I62a8162bf96d51f7252cfefbffc1a46010a3a612
    Closes-Bug: #1792313


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1792313

Title:
  Only one NVMe connection may be functional on Compute node

Status in OpenStack Compute (nova):
  Fix Released
Status in os-brick:
  In Progress

Bug description:
  Only one NVMe connection is active and working properly on the same Compute.
  When I try to attach second volume to 2nd VM on the same Compute node, the operation fails.

  Nova log shows error when executing "nvme list" (exit code non-zero)

  Reproduction:
  1. Deploy tripleO master on 3 nodes
  - 1st host: Controller and NVMf target as cinder backend 
  - 2nd and 3rd host: Compute nodes
  2. Spawn VM-1, create volume and attach volume to VM-1
  3. Spawn 2nd VM-2 on the same compute node, create new volume and attach the volume to VM-2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1792313/+subscriptions