yahoo-eng-team team mailing list archive

[OpenStack Infra <1792313@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/602332
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=fab367cc265593ac7b46feca8cb13da1385a3d03
Submitter: Zuul
Branch:    master

commit fab367cc265593ac7b46feca8cb13da1385a3d03
Author: Hamdy Khader <hamdyk@xxxxxxxxxxxx>
Date:   Thu Sep 13 14:38:11 2018 +0300

    Retry executing command "nvme list" when fail
    
    Only one NVMe connection can be active on the same Compute node, when
    initiator side has more than one connection then new connection is made,
    results of the new connected device is not instantaneous.
    
    Fixing this issue requires retry and sleep when executing command
    "nvme list" to retrieve the newly connected device.
    
    Change-Id: I6b70140be7023770b83603de723d6d2de3ebb747
    Closes-Bug: #1792313


** Changed in: os-brick
       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:
  Fix Released

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