yahoo-eng-team team mailing list archive

[OpenStack Infra <2012365@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/nova/+/877446
Committed: https://opendev.org/openstack/nova/commit/a8f81d5f08692c16d538af3197460d9426cc00a1
Submitter: "Zuul (22348)"
Branch:    master

commit a8f81d5f08692c16d538af3197460d9426cc00a1
Author: Amit Uniyal <auniyal@xxxxxxxxxx>
Date:   Wed Mar 15 05:07:28 2023 +0000

    Disconnecting volume from the compute host
    
    cmd nova-manage volume_attachment refresh vm-id vol-id connetor
    
    There were cases where the instance said to live in compute#1 but the
    connection_info in the BDM record was for compute#2, and when the script
    called `remote_volume_connection` then nova would call os-brick on
    compute#1 (the wrong node) and try to detach it.
    
    In some case os-brick would mistakenly think that the volume was
    attached (because the target and lun matched an existing volume on the
    host) and would try to disconnect, resulting in errors on the compute
    logs.
    
    - Added HostConflict exception
    - Fixes dedent in cmd/manange.py
    - Updates nova-mange doc
    
    Closes-Bug: #2012365
    Change-Id: I21109752ff1c56d3cefa58fcd36c68bf468e0a73


** 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/2012365

Title:
  Issues with nova-manage volume_attachment subcommand

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Downstream bug report from Red Hat Bugzilla against Train:
  https://bugzilla.redhat.com/show_bug.cgi?id=2161733

  1 - fix handling of instance locking
      Add a context manager for locking and unlocking instance for volume attachement refresh cmd.

  2 - disconnecting the volume from the correct host
      Verify if instance is attached to correct compute host before removing volume connection.

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