Bug 1542795 - Live Migration failure: unsupported configuration: Target device drive address 0:0:0 does not match source 0:0:1
Summary: Live Migration failure: unsupported configuration: Target device drive addres...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z8
: 10.0 (Newton)
Assignee: Sahid Ferdjaoui
QA Contact: Archit Modi
URL:
Whiteboard:
Depends On:
Blocks: 1544475
TreeView+ depends on / blocked
 
Reported: 2018-02-07 02:26 UTC by rohit londhe
Modified: 2022-08-16 11:17 UTC (History)
17 users (show)

Fixed In Version: openstack-nova-14.1.0-10.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1544475 (view as bug list)
Environment:
Last Closed: 2018-05-17 15:33:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-4858 0 None None None 2022-08-16 11:17:58 UTC
Red Hat Knowledge Base (Solution) 3465611 0 None None None 2018-05-31 17:54:00 UTC
Red Hat Product Errata RHBA-2018:1595 0 None None None 2018-05-17 15:34:56 UTC

Description rohit londhe 2018-02-07 02:26:40 UTC
Description of problem:

Facing issues while live migrating instance.

IHAC who is facing the same issue while live migrating instances with non-bootable cinder volume.

[centos@server shared]$ nova live-migration 23bb111b-952f-486f-acf0-09443529ebbb overcloud-compute-10.cloud.lt (FROM compute-7)
[centos@server shared]$ watch -n 30 openstack  server show 23bb111b-952f-486f-acf0-09443529ebbb # FAIL

-------
2018-01-19 16:04:41.403 3431 INFO nova.virt.libvirt.migration [req-f9b413e2-be34-4219-882b-e9df6e09007f 59315969bcbc4c7e8f87cdea69ba5d73 27fd33c29c9f41509f46a35657fbbce0 - - -] [instance: 23bb111b-952f-486f-acf0-09443529ebbb] Increasing downtime to 46 ms after 0 sec elapsed time
2018-01-19 16:04:41.788 3431 INFO nova.virt.libvirt.driver [req-f9b413e2-be34-4219-882b-e9df6e09007f 59315969bcbc4c7e8f87cdea69ba5d73 27fd33c29c9f41509f46a35657fbbce0 - - -] [instance: 23bb111b-952f-486f-acf0-09443529ebbb] Migration running for 0 secs, memory 100% remaining; (bytes processed=0, remaining=0, total=0)
2018-01-19 16:04:42.012 3431 ERROR nova.virt.libvirt.driver [req-f9b413e2-be34-4219-882b-e9df6e09007f 59315969bcbc4c7e8f87cdea69ba5d73 27fd33c29c9f41509f46a35657fbbce0 - - -] [instance: 23bb111b-952f-486f-acf0-09443529ebbb] Live Migration failure: unsupported configuration: Target device drive address 0:0:0 does not match source 0:0:1
2018-01-19 16:04:42.290 3431 ERROR nova.virt.libvirt.driver [req-f9b413e2-be34-4219-882b-e9df6e09007f 59315969bcbc4c7e8f87cdea69ba5d73 27fd33c29c9f41509f46a35657fbbce0 - - -] [instance: 23bb111b-952f-486f-acf0-09443529ebbb] Migration operation has aborted
---------

Storage backend: have iSCSI and Huawei storage below iSCSI.

Version-Release number of selected component (if applicable):

openstack-nova-migration-14.0.8-5.el7ost.noarch
openstack-nova-api-14.0.8-5.el7ost.noarch
puppet-nova-9.6.0-2.el7ost.noarch
python-novaclient-6.0.2-1.el7ost.noarch
python-nova-14.0.8-5.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create a non-bootable volume
2. Attached it to an instance
3. nova --debug live-migration <instace> <compute host>

Actual results:

Live migration is failing with the below error:
 
"Live Migration failure: unsupported configuration: Target device drive address 0:0:0 does not match source 0:0:1"

Expected results:

Instance should get migrated with non-bootable instance attached to it.

Additional info:

Detaching the cinder volume the instance is successfully migrated and we again re-attached the volume to the migrated instance.

Comment 2 Ruslanas Gžibovskis 2018-02-07 11:53:42 UTC
(In reply to rohit londhe from comment #0)
> Description of problem:
> 
> Facing issues while live migrating instance.
> 
> IHAC who is facing the same issue while live migrating instances with
> non-bootable cinder volume.
> 
> [centos@server shared]$ nova live-migration
> 23bb111b-952f-486f-acf0-09443529ebbb overcloud-compute-10.cloud.lt (FROM
> compute-7)
> [centos@server shared]$ watch -n 30 openstack  server show
> 23bb111b-952f-486f-acf0-09443529ebbb # FAIL
> 
> -------
> 2018-01-19 16:04:41.403 3431 INFO nova.virt.libvirt.migration
> [req-f9b413e2-be34-4219-882b-e9df6e09007f 59315969bcbc4c7e8f87cdea69ba5d73
> 27fd33c29c9f41509f46a35657fbbce0 - - -] [instance:
> 23bb111b-952f-486f-acf0-09443529ebbb] Increasing downtime to 46 ms after 0
> sec elapsed time
> 2018-01-19 16:04:41.788 3431 INFO nova.virt.libvirt.driver
> [req-f9b413e2-be34-4219-882b-e9df6e09007f 59315969bcbc4c7e8f87cdea69ba5d73
> 27fd33c29c9f41509f46a35657fbbce0 - - -] [instance:
> 23bb111b-952f-486f-acf0-09443529ebbb] Migration running for 0 secs, memory
> 100% remaining; (bytes processed=0, remaining=0, total=0)
> 2018-01-19 16:04:42.012 3431 ERROR nova.virt.libvirt.driver
> [req-f9b413e2-be34-4219-882b-e9df6e09007f 59315969bcbc4c7e8f87cdea69ba5d73
> 27fd33c29c9f41509f46a35657fbbce0 - - -] [instance:
> 23bb111b-952f-486f-acf0-09443529ebbb] Live Migration failure: unsupported
> configuration: Target device drive address 0:0:0 does not match source 0:0:1
> 2018-01-19 16:04:42.290 3431 ERROR nova.virt.libvirt.driver
> [req-f9b413e2-be34-4219-882b-e9df6e09007f 59315969bcbc4c7e8f87cdea69ba5d73
> 27fd33c29c9f41509f46a35657fbbce0 - - -] [instance:
> 23bb111b-952f-486f-acf0-09443529ebbb] Migration operation has aborted
> ---------
> 
> Storage backend: have iSCSI and Huawei storage below iSCSI.
> 
> Version-Release number of selected component (if applicable):
> 
> openstack-nova-migration-14.0.8-5.el7ost.noarch
> openstack-nova-api-14.0.8-5.el7ost.noarch
> puppet-nova-9.6.0-2.el7ost.noarch
> python-novaclient-6.0.2-1.el7ost.noarch
> python-nova-14.0.8-5.el7ost.noarch
> 
> How reproducible:
> 100%
> 
> Steps to Reproduce:
> 1. Create a non-bootable volume
> 2. Attached it to an instance
> 3. nova --debug live-migration <instace> <compute host>
> 
> Actual results:
> 
> Live migration is failing with the below error:
>  
> "Live Migration failure: unsupported configuration: Target device drive
> address 0:0:0 does not match source 0:0:1"
> 
> Expected results:
> 
> Instance should get migrated with non-bootable instance attached to it.
> 
> Additional info:
> 
> Detaching the cinder volume the instance is successfully migrated and we
> again re-attached the volume to the migrated instance.

[stack@undercloud ~]$ openstack image show b4ebdecd-559b-4c51-9f43-1db278edf10c
+------------------+--------------------------------------------------------------------------------------------------------+
| Field            | Value                                                                                                  |
+------------------+--------------------------------------------------------------------------------------------------------+
| checksum         | 90956b2310c742b42e80c5eee9e6efb4                                                                       |
| container_format | bare                                                                                                   |
| created_at       | 2017-11-27T13:26:06Z                                                                                   |
| disk_format      | qcow2                                                                                                  |
| file             | /v2/images/b4ebdecd-559b-4c51-9f43-1db278edf10c/file                                                   |
| id               | b4ebdecd-559b-4c51-9f43-1db278edf10c                                                                   |
| min_disk         | 10                                                                                                     |
| min_ram          | 1024                                                                                                   |
| name             | CentOS 7                                                                                               |
| owner            | 0810XXXXXXXXXXXXXXXXXXXXXXXXX                                                                       |
| properties       | description='The login account is centos. CentOS-7-x86_64-GenericCloud.qcow2 2017-09-13 00:31',        |
|                  | direct_url='file:///var/lib/glance/images/b4ebdecd-559b-4c51-9f43-1db278edf10c', hw_disk_bus='scsi',   |
|                  | hw_qemu_guest_agent='yes', hw_scsi_model='virtio-scsi', hw_video_model='qxl', hw_video_ram='64',       |
|                  | hw_vif_model='virtio', hw_vif_multiqueue_enabled='true', os_distro='centos', os_require_quiesce='true' |
| protected        | False                                                                                                  |
| schema           | /v2/schemas/image                                                                                      |
| size             | 854851584                                                                                              |
| status           | active                                                                                                 |
| tags             |                                                                                                        |
| updated_at       | 2017-11-27T15:47:09Z                                                                                   |
| virtual_size     | None                                                                                                   |
| visibility       | public                                                                                                 |
+------------------+--------------------------------------------------------------------------------------------------------+

Comment 4 wesun 2018-03-23 21:41:18 UTC
This is same bug as reported @ https://bugs.launchpad.net/nova/+bug/1715569. The upstream dix is @ https://review.openstack.org/#/c/518022. Please backport the commit to OSP-10.

Comment 5 wesun 2018-03-23 21:46:57 UTC
Please ignore my last comment if openstack-nova-14.1.0-10.el7ost has been released for OSP10.

Comment 6 Ruslanas Gžibovskis 2018-03-26 07:06:38 UTC
I see only 14.1.0-3.el7ost

[root@overcloud-huaweicompute-0 heat-admin]# yum list | grep openstack-nova
openstack-nova-api.noarch        1:14.0.8-5.el7ost      @rhos-10.0-signed
openstack-nova-cert.noarch       1:14.0.8-5.el7ost      @rhos-10.0-signed
openstack-nova-common.noarch     1:14.0.8-5.el7ost      @rhos-10.0-signed
openstack-nova-compute.noarch    1:14.0.8-5.el7ost      @rhos-10.0-signed
openstack-nova-conductor.noarch  1:14.0.8-5.el7ost      @rhos-10.0-signed
openstack-nova-console.noarch    1:14.0.8-5.el7ost      @rhos-10.0-signed
openstack-nova-migration.noarch  1:14.0.8-5.el7ost      @rhos-10.0-signed
openstack-nova-novncproxy.noarch 1:14.0.8-5.el7ost      @rhos-10.0-signed
openstack-nova-scheduler.noarch  1:14.0.8-5.el7ost      @rhos-10.0-signed
openstack-nova.noarch            1:14.1.0-3.el7ost      rhel-7-server-openstack-10-rpms
openstack-nova-api.noarch        1:14.1.0-3.el7ost      rhel-7-server-openstack-10-rpms
openstack-nova-cells.noarch      1:14.1.0-3.el7ost      rhel-7-server-openstack-10-rpms
openstack-nova-cert.noarch       1:14.1.0-3.el7ost      rhel-7-server-openstack-10-rpms
openstack-nova-common.noarch     1:14.1.0-3.el7ost      rhel-7-server-openstack-10-rpms
openstack-nova-compute.noarch    1:14.1.0-3.el7ost      rhel-7-server-openstack-10-rpms
openstack-nova-conductor.noarch  1:14.1.0-3.el7ost      rhel-7-server-openstack-10-rpms
openstack-nova-console.noarch    1:14.1.0-3.el7ost      rhel-7-server-openstack-10-rpms
openstack-nova-migration.noarch  1:14.1.0-3.el7ost      rhel-7-server-openstack-10-rpms
openstack-nova-network.noarch    1:14.1.0-3.el7ost      rhel-7-server-openstack-10-rpms
openstack-nova-novncproxy.noarch 1:14.1.0-3.el7ost      rhel-7-server-openstack-10-rpms
openstack-nova-placement-api.noarch
openstack-nova-scheduler.noarch  1:14.1.0-3.el7ost      rhel-7-server-openstack-10-rpms
openstack-nova-serialproxy.noarch
openstack-nova-spicehtml5proxy.noarch
[root@overcloud-huaweicompute-0 heat-admin]#

Comment 22 errata-xmlrpc 2018-05-17 15:33:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1595


Note You need to log in before you can comment on or make changes to this bug.