| 2015-07-21 04:36:51 |
Ghanshyam Mann |
bug |
|
|
added bug |
| 2015-07-21 04:40:12 |
Ghanshyam Mann |
tempest: assignee |
|
Ghanshyam Mann (ghanshyammann) |
|
| 2015-07-21 04:41:30 |
Ghanshyam Mann |
description |
Sometimes, test_live_block_migration failes on multinode job (gate-tempest-dsvm-multinode-full).
http://logs.openstack.org/91/202391/5/check/gate-tempest-dsvm-multinode-full/f838b41/logs/testr_results.html.gz
Here migration is aborted with error
2015-07-17 04:10:35.927 ERROR nova.virt.libvirt.driver [req-9579e902-93e5-4960-a01d-d1c4c30e64f4 tempest-LiveBlockMigrationTestJSON-824752007 tempest-LiveBlockMigrationTestJSON-153657043] [instance: 6404173e-bb22-43a8-9894-447e2f12591a] Live Migration failure: operation failed: Failed to connect to remote libvirt URI qemu+ssh://stack@devstack-trusty-2-node-hpcloud-b3-3757707/system: Cannot recv data: ssh: Could not resolve hostname devstack-trusty-2-node-hpcloud-b3-3757707: Name or service not known: Connection reset by peer
2015-07-17 04:10:36.421 ERROR nova.virt.libvirt.driver [req-9579e902-93e5-4960-a01d-d1c4c30e64f4 tempest-LiveBlockMigrationTestJSON-824752007 tempest-LiveBlockMigrationTestJSON-153657043] [instance: 6404173e-bb22-43a8-9894-447e2f12591a] Migration operation has aborted
And nova put server to active state. After server state is changed from "MIGRATING" to "ACTIVE", Tempest checks target host and fails.
May be Nova behavior of putting server back to Active even migration failed is correct (so that user can still use server on old host) but not sure.
Here we can improve Tempest tests by addition check to list migrations and check the migration status. This will be helpful in debugging. |
Sometimes, test_live_block_migration failes on multinode job (gate-tempest-dsvm-multinode-full).
http://logs.openstack.org/91/202391/5/check/gate-tempest-dsvm-multinode-full/f838b41/logs/testr_results.html.gz
Here migration is aborted with error
2015-07-17 04:10:29.375 ERROR nova.virt.libvirt.driver [req-6c97293d-b191-417e-9e77-d4967b5bfc5d tempest-LiveBlockMigrationTestJSON-824752007 tempest-LiveBlockMigrationTestJSON-153657043] [instance: 6404173e-bb22-43a8-9894-447e2f12591a] Live Migration failure: operation failed: Failed to connect to remote libvirt URI qemu+ssh://stack@devstack-trusty-2-node-hpcloud-b3-3757707/system: Cannot recv data: ssh: Could not resolve hostname devstack-trusty-2-node-hpcloud-b3-3757707: Name or service not known: Connection reset by peer
2015-07-17 04:10:29.812 ERROR nova.virt.libvirt.driver [req-6c97293d-b191-417e-9e77-d4967b5bfc5d tempest-LiveBlockMigrationTestJSON-824752007 tempest-LiveBlockMigrationTestJSON-153657043] [instance: 6404173e-bb22-43a8-9894-447e2f12591a] Migration operation has aborted
And nova put server to active state. After server state is changed from "MIGRATING" to "ACTIVE", Tempest checks target host and fails.
May be Nova behavior of putting server back to Active even migration failed is correct (so that user can still use server on old host) but not sure.
Here we can improve Tempest tests by addition check to list migrations and check the migration status. This will be helpful in debugging. |
|
| 2015-07-21 07:04:26 |
Ghanshyam Mann |
description |
Sometimes, test_live_block_migration failes on multinode job (gate-tempest-dsvm-multinode-full).
http://logs.openstack.org/91/202391/5/check/gate-tempest-dsvm-multinode-full/f838b41/logs/testr_results.html.gz
Here migration is aborted with error
2015-07-17 04:10:29.375 ERROR nova.virt.libvirt.driver [req-6c97293d-b191-417e-9e77-d4967b5bfc5d tempest-LiveBlockMigrationTestJSON-824752007 tempest-LiveBlockMigrationTestJSON-153657043] [instance: 6404173e-bb22-43a8-9894-447e2f12591a] Live Migration failure: operation failed: Failed to connect to remote libvirt URI qemu+ssh://stack@devstack-trusty-2-node-hpcloud-b3-3757707/system: Cannot recv data: ssh: Could not resolve hostname devstack-trusty-2-node-hpcloud-b3-3757707: Name or service not known: Connection reset by peer
2015-07-17 04:10:29.812 ERROR nova.virt.libvirt.driver [req-6c97293d-b191-417e-9e77-d4967b5bfc5d tempest-LiveBlockMigrationTestJSON-824752007 tempest-LiveBlockMigrationTestJSON-153657043] [instance: 6404173e-bb22-43a8-9894-447e2f12591a] Migration operation has aborted
And nova put server to active state. After server state is changed from "MIGRATING" to "ACTIVE", Tempest checks target host and fails.
May be Nova behavior of putting server back to Active even migration failed is correct (so that user can still use server on old host) but not sure.
Here we can improve Tempest tests by addition check to list migrations and check the migration status. This will be helpful in debugging. |
Sometimes, test_live_block_migration fails on multinode job (gate-tempest-dsvm-multinode-full).
http://logs.openstack.org/91/202391/5/check/gate-tempest-dsvm-multinode-full/f838b41/logs/testr_results.html.gz
Here migration is aborted with error
2015-07-17 04:10:29.375 ERROR nova.virt.libvirt.driver [req-6c97293d-b191-417e-9e77-d4967b5bfc5d tempest-LiveBlockMigrationTestJSON-824752007 tempest-LiveBlockMigrationTestJSON-153657043] [instance: 6404173e-bb22-43a8-9894-447e2f12591a] Live Migration failure: operation failed: Failed to connect to remote libvirt URI qemu+ssh://stack@devstack-trusty-2-node-hpcloud-b3-3757707/system: Cannot recv data: ssh: Could not resolve hostname devstack-trusty-2-node-hpcloud-b3-3757707: Name or service not known: Connection reset by peer
2015-07-17 04:10:29.812 ERROR nova.virt.libvirt.driver [req-6c97293d-b191-417e-9e77-d4967b5bfc5d tempest-LiveBlockMigrationTestJSON-824752007 tempest-LiveBlockMigrationTestJSON-153657043] [instance: 6404173e-bb22-43a8-9894-447e2f12591a] Migration operation has aborted
And nova put server to active state. After server state is changed from "MIGRATING" to "ACTIVE", Tempest checks target host and fails.
May be Nova behavior of putting server back to Active even migration failed is correct (so that user can still use server on old host) but not sure.
Here we can improve Tempest tests by addition check to list migrations and check the migration status. This will be helpful in debugging. |
|
| 2015-07-21 07:12:21 |
OpenStack Infra |
tempest: status |
New |
In Progress |
|
| 2015-08-13 15:49:24 |
OpenStack Infra |
tempest: status |
In Progress |
Fix Released |
|
