yahoo-eng-team team mailing list archive

[OpenStack Infra <1945983@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/devstack/+/812391
Committed: https://opendev.org/openstack/devstack/commit/714826d1a27085ba2384ca495c876588d77f0d27
Submitter: "Zuul (22348)"
Branch:    master

commit 714826d1a27085ba2384ca495c876588d77f0d27
Author: Lee Yarwood <lyarwood@xxxxxxxxxx>
Date:   Mon Oct 4 18:07:17 2021 +0100

    nova: Ensure each compute uses a unique iSCSI initiator
    
    The current initiator name embedded in our CI images is not unique at
    present and can often cause failures during live migrations with
    attached volumes. This change ensures the name is unique by running
    iscsi-iname again and overwriting the existing name.
    
    We could potentially do this during the image build process itself but
    given that devstack systems are not supposed to be multi-purpose this
    should be safe to do during the devstack run.
    
    Closes-Bug: #1945983
    Change-Id: I9ed26a17858df96c04be9ae52bf2e33e023869a5


** Changed in: devstack
       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/1945983

Title:
  Duplicate iSCSI initiators causing live migration failures

Status in devstack:
  Fix Released
Status in OpenStack Compute (nova):
  Incomplete

Bug description:
  Description
  ===========

  See c#2 for the actual issue here.

  Steps to reproduce
  ==================

  LiveAutoBlockMigrationV225Test:test_live_migration_with_trunk or any
  live migration test with trunk ports fails during cleanup.

  Expected result
  ===============

  Both the test and cleanup pass without impacting libvirtd.

  Actual result
  =============

  The test passes, cleanup locks up the single thread handling the
  libvirtd event loop in 6.0.0.

  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
    list for all releases: http://docs.openstack.org/releases/

     stable/xena and master

  2. Which hypervisor did you use?
     (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
     What's the version of that?

     libvirt (6.0.0) and QEMU

  2. Which storage type did you use?
     (For example: Ceph, LVM, GPFS, ...)
     What's the version of that?

     N/A

  3. Which networking type did you use?
     (For example: nova-network, Neutron with OpenVSwitch, ...)

      Trunk ports.

  Logs & Configs
  ==============

  Initially discovered and discussed as part of
  https://bugs.launchpad.net/nova/+bug/1912310 where the locking up
  within libvirtd causes other tests to then fail.

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