yahoo-eng-team team mailing list archive

Thread
Date
[Bug 1625462] [NEW] The value of migration.dest_node is incorrect after finish_revert_resize successfully

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Charlotte Han <han.rong3@xxxxxxxxxx>
Date: Tue, 20 Sep 2016 06:07:53 -0000
Reply-to: Bug 1625462 <1625462@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
Public bug reported:

I have two host: tecs-controller-node and tecs-OpenStack-Nova.

1. I did migrate action, then instance's state is as follow:
+--------------------------------------+----------+---------------+------------+-------------+--------------------------------+
| ID                                   | Name     | Status        | Task State | Power State | Networks                       |
+--------------------------------------+----------+---------------+------------+-------------+--------------------------------+
| ea40a5f7-d92b-4ad6-94c0-a18f2465519e | hanrong1 | VERIFY_RESIZE | -          | Running     | public=172.24.4.2, 2001:db8::8 |
+--------------------------------------+----------+---------------+------------+-------------+--------------------------------+


2. I did look at migrations' table for instance source_node and dest_node.

mysql> select * from migrations where instance_uuid='ea40a5f7-d92b-4ad6-94c0-a18f2465519e';
+---------------------+---------------------+------------+----+----------------------+---------------------+--------------+----------+--------------------------------------+----------------------+----------------------+----------------------+---------------------+---------+----------------+--------+--------------+------------------+------------------+------------+----------------+----------------+
| created_at          | updated_at          | deleted_at | id | source_compute       | dest_compute        | dest_host    | status   | instance_uuid                        | old_instance_type_id | new_instance_type_id | source_node          | dest_node           | deleted | migration_type | hidden | memory_total | memory_processed | memory_remaining | disk_total | disk_processed | disk_remaining |
+---------------------+---------------------+------------+----+----------------------+---------------------+--------------+----------+--------------------------------------+----------------------+----------------------+----------------------+---------------------+---------+----------------+--------+--------------+------------------+------------------+------------+----------------+----------------+
| 2016-09-20 02:38:24 | 2016-09-20 02:38:58 | NULL       |  1 | tecs-controller-node | tecs-OpenStack-Nova | 192.168.1.60 | finished | ea40a5f7-d92b-4ad6-94c0-a18f2465519e |                    6 |                    6 | tecs-controller-node | tecs-OpenStack-Nova |       0 | migration      |      0 |         NULL |             NULL |             NULL |       NULL |           NULL |           NULL |
+---------------------+---------------------+------------+----+----------------------+---------------------+--------------+----------+--------------------------------------+----------------------+----------------------+----------------------+---------------------+---------+----------------+--------+--------------+------------------+------------------+------------+----------------+----------------+

source_compute: tecs-controller-node
source_node: tecs-controller-node
dest_compute:tecs-OpenStack-Nova
dest_node: tecs-OpenStack-Nova

3. I did resize-revert action
stack@tecs-controller-node:~$ nova resize-revert hanrong1
stack@tecs-controller-node:~$ nova list
+--------------------------------------+----------+---------------+------------------+-------------+--------------------------------+
| ID                                   | Name     | Status        | Task State       | Power State | Networks                       |
+--------------------------------------+----------+---------------+------------------+-------------+--------------------------------+
| ea40a5f7-d92b-4ad6-94c0-a18f2465519e | hanrong1 | REVERT_RESIZE | resize_reverting | Running     | public=172.24.4.2, 2001:db8::8 |
+--------------------------------------+----------+---------------+------------------+-------------+--------------------------------+
stack@tecs-controller-node:~$ nova list
+--------------------------------------+----------+--------+------------+-------------+--------------------------------+
| ID                                   | Name     | Status | Task State | Power State | Networks                       |
+--------------------------------------+----------+--------+------------+-------------+--------------------------------+
| ea40a5f7-d92b-4ad6-94c0-a18f2465519e | hanrong1 | ACTIVE | -          | Running     | public=172.24.4.2, 2001:db8::8 |
+--------------------------------------+----------+--------+------------+-------------+--------------------------------+


4. I did look at migrations' table for instance source_node and dest_node.
mysql> select * from migrations where instance_uuid='ea40a5f7-d92b-4ad6-94c0-a18f2465519e';
+---------------------+---------------------+------------+----+----------------------+----------------------+--------------+----------+--------------------------------------+----------------------+----------------------+----------------------+---------------------+---------+----------------+--------+--------------+------------------+------------------+------------+----------------+----------------+
| created_at          | updated_at          | deleted_at | id | source_compute       | dest_compute         | dest_host    | status   | instance_uuid                        | old_instance_type_id | new_instance_type_id | source_node          | dest_node           | deleted | migration_type | hidden | memory_total | memory_processed | memory_remaining | disk_total | disk_processed | disk_remaining |
+---------------------+---------------------+------------+----+----------------------+----------------------+--------------+----------+--------------------------------------+----------------------+----------------------+----------------------+---------------------+---------+----------------+--------+--------------+------------------+------------------+------------+----------------+----------------+
| 2016-09-20 02:38:24 | 2016-09-20 03:52:01 | NULL       |  1 | tecs-controller-node | tecs-controller-node | 192.168.1.60 | reverted | ea40a5f7-d92b-4ad6-94c0-a18f2465519e |                    6 |                    6 | tecs-controller-node | tecs-OpenStack-Nova |       0 | migration      |      0 |         NULL |             NULL |             NULL |       NULL |           NULL |           NULL |
+---------------------+---------------------+------------+----+----------------------+----------------------+--------------+----------+--------------------------------------+----------------------+----------------------+----------------------+---------------------+---------+----------------+--------+--------------+------------------+------------------+------------+----------------+----------------+

source_compute: tecs-controller-node
source_node: tecs-controller-node
dest_compute:tecs-controller-node
dest_node: tecs-OpenStack-Nova


dest_node is not incorrect.

Expected result
===============

source_compute: tecs-controller-node
source_node: tecs-controller-node
dest_compute:tecs-controller-node
dest_node: tecs-controller-node

Environment
===========
1. git log -1
commit c6a07f5f0cbd978cc2a23214ddf4ecd520ce8335
Merge: 14d816e 09627f2
Author: Jenkins <jenkins@xxxxxxxxxxxxxxxxxxxx>
Date:   Wed Sep 7 22:36:12 2016 +0000

    Merge "[placement] Allow inventory to violate allo

2. Which hypervisor did you use?
libvirt + kvm

** 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/1625462

Title:
  The value of migration.dest_node is incorrect after
  finish_revert_resize successfully

Status in OpenStack Compute (nova):
  New

Bug description:
  I have two host: tecs-controller-node and tecs-OpenStack-Nova.

  1. I did migrate action, then instance's state is as follow:
  +--------------------------------------+----------+---------------+------------+-------------+--------------------------------+
  | ID                                   | Name     | Status        | Task State | Power State | Networks                       |
  +--------------------------------------+----------+---------------+------------+-------------+--------------------------------+
  | ea40a5f7-d92b-4ad6-94c0-a18f2465519e | hanrong1 | VERIFY_RESIZE | -          | Running     | public=172.24.4.2, 2001:db8::8 |
  +--------------------------------------+----------+---------------+------------+-------------+--------------------------------+

  
  2. I did look at migrations' table for instance source_node and dest_node.

  mysql> select * from migrations where instance_uuid='ea40a5f7-d92b-4ad6-94c0-a18f2465519e';
  +---------------------+---------------------+------------+----+----------------------+---------------------+--------------+----------+--------------------------------------+----------------------+----------------------+----------------------+---------------------+---------+----------------+--------+--------------+------------------+------------------+------------+----------------+----------------+
  | created_at          | updated_at          | deleted_at | id | source_compute       | dest_compute        | dest_host    | status   | instance_uuid                        | old_instance_type_id | new_instance_type_id | source_node          | dest_node           | deleted | migration_type | hidden | memory_total | memory_processed | memory_remaining | disk_total | disk_processed | disk_remaining |
  +---------------------+---------------------+------------+----+----------------------+---------------------+--------------+----------+--------------------------------------+----------------------+----------------------+----------------------+---------------------+---------+----------------+--------+--------------+------------------+------------------+------------+----------------+----------------+
  | 2016-09-20 02:38:24 | 2016-09-20 02:38:58 | NULL       |  1 | tecs-controller-node | tecs-OpenStack-Nova | 192.168.1.60 | finished | ea40a5f7-d92b-4ad6-94c0-a18f2465519e |                    6 |                    6 | tecs-controller-node | tecs-OpenStack-Nova |       0 | migration      |      0 |         NULL |             NULL |             NULL |       NULL |           NULL |           NULL |
  +---------------------+---------------------+------------+----+----------------------+---------------------+--------------+----------+--------------------------------------+----------------------+----------------------+----------------------+---------------------+---------+----------------+--------+--------------+------------------+------------------+------------+----------------+----------------+

  source_compute: tecs-controller-node
  source_node: tecs-controller-node
  dest_compute:tecs-OpenStack-Nova
  dest_node: tecs-OpenStack-Nova

  3. I did resize-revert action
  stack@tecs-controller-node:~$ nova resize-revert hanrong1
  stack@tecs-controller-node:~$ nova list
  +--------------------------------------+----------+---------------+------------------+-------------+--------------------------------+
  | ID                                   | Name     | Status        | Task State       | Power State | Networks                       |
  +--------------------------------------+----------+---------------+------------------+-------------+--------------------------------+
  | ea40a5f7-d92b-4ad6-94c0-a18f2465519e | hanrong1 | REVERT_RESIZE | resize_reverting | Running     | public=172.24.4.2, 2001:db8::8 |
  +--------------------------------------+----------+---------------+------------------+-------------+--------------------------------+
  stack@tecs-controller-node:~$ nova list
  +--------------------------------------+----------+--------+------------+-------------+--------------------------------+
  | ID                                   | Name     | Status | Task State | Power State | Networks                       |
  +--------------------------------------+----------+--------+------------+-------------+--------------------------------+
  | ea40a5f7-d92b-4ad6-94c0-a18f2465519e | hanrong1 | ACTIVE | -          | Running     | public=172.24.4.2, 2001:db8::8 |
  +--------------------------------------+----------+--------+------------+-------------+--------------------------------+

  
  4. I did look at migrations' table for instance source_node and dest_node.
  mysql> select * from migrations where instance_uuid='ea40a5f7-d92b-4ad6-94c0-a18f2465519e';
  +---------------------+---------------------+------------+----+----------------------+----------------------+--------------+----------+--------------------------------------+----------------------+----------------------+----------------------+---------------------+---------+----------------+--------+--------------+------------------+------------------+------------+----------------+----------------+
  | created_at          | updated_at          | deleted_at | id | source_compute       | dest_compute         | dest_host    | status   | instance_uuid                        | old_instance_type_id | new_instance_type_id | source_node          | dest_node           | deleted | migration_type | hidden | memory_total | memory_processed | memory_remaining | disk_total | disk_processed | disk_remaining |
  +---------------------+---------------------+------------+----+----------------------+----------------------+--------------+----------+--------------------------------------+----------------------+----------------------+----------------------+---------------------+---------+----------------+--------+--------------+------------------+------------------+------------+----------------+----------------+
  | 2016-09-20 02:38:24 | 2016-09-20 03:52:01 | NULL       |  1 | tecs-controller-node | tecs-controller-node | 192.168.1.60 | reverted | ea40a5f7-d92b-4ad6-94c0-a18f2465519e |                    6 |                    6 | tecs-controller-node | tecs-OpenStack-Nova |       0 | migration      |      0 |         NULL |             NULL |             NULL |       NULL |           NULL |           NULL |
  +---------------------+---------------------+------------+----+----------------------+----------------------+--------------+----------+--------------------------------------+----------------------+----------------------+----------------------+---------------------+---------+----------------+--------+--------------+------------------+------------------+------------+----------------+----------------+

  source_compute: tecs-controller-node
  source_node: tecs-controller-node
  dest_compute:tecs-controller-node
  dest_node: tecs-OpenStack-Nova

  
  dest_node is not incorrect.

  Expected result
  ===============

  source_compute: tecs-controller-node
  source_node: tecs-controller-node
  dest_compute:tecs-controller-node
  dest_node: tecs-controller-node

  Environment
  ===========
  1. git log -1
  commit c6a07f5f0cbd978cc2a23214ddf4ecd520ce8335
  Merge: 14d816e 09627f2
  Author: Jenkins <jenkins@xxxxxxxxxxxxxxxxxxxx>
  Date:   Wed Sep 7 22:36:12 2016 +0000

      Merge "[placement] Allow inventory to violate allo

  2. Which hypervisor did you use?
  libvirt + kvm

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

[Bug 1625462] Re: The value of migration.dest_compute is incorrect after resize_revert operation successfully
From: Maciej Szankin, 2016-11-29