← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1825354] [NEW] swap_volume failed

 

Public bug reported:

Description
===========
volume migration failed but have no feedback

Steps to reproduce
==================
* I tried to migrate an attached volume.
    
    $ cinder migrate 7de63101-7616-47ce-b6ed-39d4df8e2907 control.az01.rocky1@ceph-rbd

* then I show the status of new volume and old volume:

    new volume:
    | migration_status               | target:7de63101-7616-47ce-b6ed-39d4df8e2907 |
    | os-vol-mig-status-attr:migstat | target:7de63101-7616-47ce-b6ed-39d4df8e2907 |
    | status                         | available                                   |

    old volume:
    | migration_status               | migrating                                |
    | os-vol-mig-status-attr:migstat | migrating                                |
    | status                         | in-use                                   |

* then I searched the nova-compute.log.

    2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97] Traceback (most recent call last):
    2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97]   File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 5723, in _swap_volume
    2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97]     mountpoint, resize_to)
    2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97]   File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1556, in swap_volume
    2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97]     raise NotImplementedError(_("Swap only supports host devices"))
    2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97] NotImplementedError: Swap only supports host devices
    2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97]

Expected result
===============
    new volume can be auto deleted,
    old volume:
    | migration_status               | None                                     |
    | os-vol-mig-status-attr:migstat | None                                     |
    | status                         | in-use                                   |

Actual result
=============
    these two volume waits for migrate success while the nova-compute.log occured ERROR.

Environment
===========
1. Exact version of OpenStack you are running. See the following
    $ rpm -qa | grep nova
    openstack-nova-conductor-18.1.0-1.el7.noarch
    openstack-nova-console-18.1.0-1.el7.noarch
    python2-novaclient-11.0.0-1.el7.noarch
    openstack-nova-compute-18.1.0-1.el7.noarch
    openstack-nova-api-18.1.0-1.el7.noarch
    openstack-nova-novncproxy-18.1.0-1.el7.noarch
    openstack-nova-common-18.1.0-1.el7.noarch
    openstack-nova-scheduler-18.1.0-1.el7.noarch
    python-nova-18.1.0-1.el7.noarch
    openstack-nova-placement-api-18.1.0-1.el7.noarch

2. Which storage type did you use?
   Ceph

3. Which networking type did you use?
   Neutron

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1825354

Title:
  swap_volume failed

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  volume migration failed but have no feedback

  Steps to reproduce
  ==================
  * I tried to migrate an attached volume.
      
      $ cinder migrate 7de63101-7616-47ce-b6ed-39d4df8e2907 control.az01.rocky1@ceph-rbd

  * then I show the status of new volume and old volume:

      new volume:
      | migration_status               | target:7de63101-7616-47ce-b6ed-39d4df8e2907 |
      | os-vol-mig-status-attr:migstat | target:7de63101-7616-47ce-b6ed-39d4df8e2907 |
      | status                         | available                                   |

      old volume:
      | migration_status               | migrating                                |
      | os-vol-mig-status-attr:migstat | migrating                                |
      | status                         | in-use                                   |

  * then I searched the nova-compute.log.

      2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97] Traceback (most recent call last):
      2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97]   File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 5723, in _swap_volume
      2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97]     mountpoint, resize_to)
      2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97]   File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1556, in swap_volume
      2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97]     raise NotImplementedError(_("Swap only supports host devices"))
      2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97] NotImplementedError: Swap only supports host devices
      2019-04-18 14:56:26.288 27737 ERROR nova.compute.manager [instance: d111dfa2-61e2-4b4d-8574-6527acf1ab97]

  Expected result
  ===============
      new volume can be auto deleted,
      old volume:
      | migration_status               | None                                     |
      | os-vol-mig-status-attr:migstat | None                                     |
      | status                         | in-use                                   |

  Actual result
  =============
      these two volume waits for migrate success while the nova-compute.log occured ERROR.

  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
      $ rpm -qa | grep nova
      openstack-nova-conductor-18.1.0-1.el7.noarch
      openstack-nova-console-18.1.0-1.el7.noarch
      python2-novaclient-11.0.0-1.el7.noarch
      openstack-nova-compute-18.1.0-1.el7.noarch
      openstack-nova-api-18.1.0-1.el7.noarch
      openstack-nova-novncproxy-18.1.0-1.el7.noarch
      openstack-nova-common-18.1.0-1.el7.noarch
      openstack-nova-scheduler-18.1.0-1.el7.noarch
      python-nova-18.1.0-1.el7.noarch
      openstack-nova-placement-api-18.1.0-1.el7.noarch

  2. Which storage type did you use?
     Ceph

  3. Which networking type did you use?
     Neutron

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