Public bug reported:
in controller+2 Compute node instance is not getting evacuated from one
compute node to other compute node. On evacuation it gets stuck with state as
rebuilding on the source node.
Below was logged in the destination compute node
(/var/log/nova/nova-compute.log):
2017-04-11 00:51:10.006 10570 INFO nova.compute.claims
[req-73b67fc8-2e29-4028-924c-2eb3d793bc79 - - - - -] [instance:
95e375bb-d030-4eb7-aa4a-e0ea5091c274] Claim successful
Which means that the resources required for evacuation were successfully
claimed. There were no logs showing rebuild activity, where as in newton for
the same activity logs(/var/log/nova/nova-compute.log) were showing as:
2017-05-25 15:47:15.612 3210 INFO nova.compute.claims
[req-363558f0-f488-4f6b-aca5-96604a317da1 38de98b17f774987ba09c5c93955f6cd
92b77d6453eb43ceaf6f127224a7021f - - -] [instance:
f6b4899a-60ff-45b7-9dfa-4b1c99158d0c] Claim successful
2017-05-25 15:47:15.803 3210 INFO nova.compute.resource_tracker
[req-363558f0-f488-4f6b-aca5-96604a317da1 38de98b17f774987ba09c5c93955f6cd
92b77d6453eb43ceaf6f127224a7021f - - -] Updating from migration
f6b4899a-60ff-45b7-9dfa-4b1c99158d0c
2017-05-25 15:47:15.830 3210 INFO nova.compute.manager
[req-363558f0-f488-4f6b-aca5-96604a317da1 38de98b17f774987ba09c5c93955f6cd
92b77d6453eb43ceaf6f127224a7021f - - -] disk not on shared storage, rebuilding
from: '598ec845-c0c0-4fd3-a5a0-b30d4d51a30a'
Steps to reproduce:
1> Create an instance on first compute node from CLI in controller node.
2> shutdown nova-compute service on first node.
3> run evacuate command for the created instance giving destination as second
node from controller node.
** Affects: nova
Importance: Undecided
Status: New
** Tags: evacuate nova
--
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/1693727
Title:
Nova evacuate instance is not working
Status in OpenStack Compute (nova):
New
Bug description:
in controller+2 Compute node instance is not getting evacuated from one
compute node to other compute node. On evacuation it gets stuck with state as
rebuilding on the source node.
Below was logged in the destination compute node
(/var/log/nova/nova-compute.log):
2017-04-11 00:51:10.006 10570 INFO nova.compute.claims
[req-73b67fc8-2e29-4028-924c-2eb3d793bc79 - - - - -] [instance:
95e375bb-d030-4eb7-aa4a-e0ea5091c274] Claim successful
Which means that the resources required for evacuation were successfully
claimed. There were no logs showing rebuild activity, where as in newton for
the same activity logs(/var/log/nova/nova-compute.log) were showing as:
2017-05-25 15:47:15.612 3210 INFO nova.compute.claims
[req-363558f0-f488-4f6b-aca5-96604a317da1 38de98b17f774987ba09c5c93955f6cd
92b77d6453eb43ceaf6f127224a7021f - - -] [instance:
f6b4899a-60ff-45b7-9dfa-4b1c99158d0c] Claim successful
2017-05-25 15:47:15.803 3210 INFO nova.compute.resource_tracker
[req-363558f0-f488-4f6b-aca5-96604a317da1 38de98b17f774987ba09c5c93955f6cd
92b77d6453eb43ceaf6f127224a7021f - - -] Updating from migration
f6b4899a-60ff-45b7-9dfa-4b1c99158d0c
2017-05-25 15:47:15.830 3210 INFO nova.compute.manager
[req-363558f0-f488-4f6b-aca5-96604a317da1 38de98b17f774987ba09c5c93955f6cd
92b77d6453eb43ceaf6f127224a7021f - - -] disk not on shared storage, rebuilding
from: '598ec845-c0c0-4fd3-a5a0-b30d4d51a30a'
Steps to reproduce:
1> Create an instance on first compute node from CLI in controller node.
2> shutdown nova-compute service on first node.
3> run evacuate command for the created instance giving destination as second
node from controller node.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1693727/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
