yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #43553
[Bug 1527553] [NEW] cells:live-migration instance with target host failed in cells
Public bug reported:
1. version
kilo 2015.1.0
2. Relevant log files:
the nova-conductor.log on cell(type:compute)
2015-12-17 14:10:48.441 6355 WARNING nova.scheduler.utils [req-dfcb2a34-ef45-4162-8af6-28235621951c f04e318acd7e4e5093c91e6dc74a28c3 53adc6d6825b43378d6ab89fc38051da - - -] Failed to compute_task_migrate_server: Compute service of api_cell!child_cell@chenling-kilo-2 is unavailable at this time.
2015-12-17 14:10:48.441 6355 WARNING nova.scheduler.utils [req-dfcb2a34-ef45-4162-8af6-28235621951c f04e318acd7e4e5093c91e6dc74a28c3 53adc6d6825b43378d6ab89fc38051da - - -] [instance: 69f74657-ba6e-4939-a7c6-e9dc3811baa5] Setting instance to ACTIVE state
3. Reproduce steps:
Environment description
i have a cell(type:api), named api_cell
two cells(type:compute) named child_cell and child_cell02.
There are two computing nodes : chenling-kilo and chenling-kilo-2 mount on cell: child_cell
There are one computing node : CL-SBCJ-5-3-4 mount on cell: child_cell02
3.1
create a new instance from image in cells, and this instance created success on compute nodes child_cell
3.2
then live-migration this instance target to child_cell02
Expected result:
live-migration success
Actual result:
live-migration failed , Log in the second quarter
4.
The log shows that :
the host name on api_cell is "api_cell!child_cell@chenling-kilo-2"
but on child_cell is "chenling-kilo-2"
when we live-migration instance with target host,
the hostname "api_cell!child_cell@chenling-kilo-2" is send to child_cell's nova-conductor.
nova-conductor check_host_is_up find "api_cell!child_cell@chenling-kilo-2" not exist and
think "Compute service of api_cell!child_cell@chenling-kilo-2 is unavailable at this time",
leads to live-migration failed
** Affects: nova
Importance: Undecided
Status: New
** Tags: cells live-migration
--
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/1527553
Title:
cells:live-migration instance with target host failed in cells
Status in OpenStack Compute (nova):
New
Bug description:
1. version
kilo 2015.1.0
2. Relevant log files:
the nova-conductor.log on cell(type:compute)
2015-12-17 14:10:48.441 6355 WARNING nova.scheduler.utils [req-dfcb2a34-ef45-4162-8af6-28235621951c f04e318acd7e4e5093c91e6dc74a28c3 53adc6d6825b43378d6ab89fc38051da - - -] Failed to compute_task_migrate_server: Compute service of api_cell!child_cell@chenling-kilo-2 is unavailable at this time.
2015-12-17 14:10:48.441 6355 WARNING nova.scheduler.utils [req-dfcb2a34-ef45-4162-8af6-28235621951c f04e318acd7e4e5093c91e6dc74a28c3 53adc6d6825b43378d6ab89fc38051da - - -] [instance: 69f74657-ba6e-4939-a7c6-e9dc3811baa5] Setting instance to ACTIVE state
3. Reproduce steps:
Environment description
i have a cell(type:api), named api_cell
two cells(type:compute) named child_cell and child_cell02.
There are two computing nodes : chenling-kilo and chenling-kilo-2 mount on cell: child_cell
There are one computing node : CL-SBCJ-5-3-4 mount on cell: child_cell02
3.1
create a new instance from image in cells, and this instance created success on compute nodes child_cell
3.2
then live-migration this instance target to child_cell02
Expected result:
live-migration success
Actual result:
live-migration failed , Log in the second quarter
4.
The log shows that :
the host name on api_cell is "api_cell!child_cell@chenling-kilo-2"
but on child_cell is "chenling-kilo-2"
when we live-migration instance with target host,
the hostname "api_cell!child_cell@chenling-kilo-2" is send to child_cell's nova-conductor.
nova-conductor check_host_is_up find "api_cell!child_cell@chenling-kilo-2" not exist and
think "Compute service of api_cell!child_cell@chenling-kilo-2 is unavailable at this time",
leads to live-migration failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1527553/+subscriptions
Follow ups