info about migration is not appropriate

[jichenjc]

nova migration information reports flavor.id not flavor.flavorid which the API requires everywhere else.

-----------+------------+----------------------------+----------------------------+
| Source Node | Dest Node | Source Compute | Dest Compute | Dest Host | Status | Instance UUID | Old Flavor | New Flavor | Created At | Updated At |
+-----------------+-----------------+-----------------+-----------------+-----------------+-----------+--------------------------------------+------------+------------+----------------------------+----------------------------+
| cloudcontroller | cloudcontroller | cloudcontroller | cloudcontroller | 192.168.122.202 | confirmed | cb7c6742-7b7a-44de-ad5a-8570ee520f9e | 2 | 15 | 2014-08-27T01:36:58.000000 | 2014-08-27T01:42:27.000000 |
| cloudcontroller | cloudcontroller | cloudcontroller | cloudcontroller | 192.168.122.202 | error | cb7c6742-7b7a-44de-ad5a-8570ee520f9e | 15 | 2 | 2014-08-28T05:03:56.000000 | 2014-08-28T05:03:57.000000 |
| cloudcontroller | cloudcontroller | cloudcontroller | cloudcontroller | 192.168.122.202 | confirmed | 2ef6c554-bffa-4ec8-adfd-9ede6ee7e389 | 2 | 15 | 2014-10-15T09:45:25.000000 | 2014-10-15T09:46:16.000000 |
| cloudcontroller | cloudcontroller | cloudcontroller | cloudcontroller | 192.168.122.202 | reverted | 2ef6c554-bffa-4ec8-adfd-9ede6ee7e389 | 15 | 2 | 2014-10-15T09:50:54.000000 | 2014-10-15T09:57:28.000000 |
| cloudcontroller | cloudcontroller | cloudcontroller | cloudcontroller | 192.168.122.202 | confirmed | 1a000511-f17b-4024-b54d-6ae3cf00673a | 17 | 19 | 2014-11-04T02:17:57.000000 | 2014-11-04T02:23:14.000000 |
| cloudcontroller | cloudcontroller | cloudcontroller | cloudcontroller | 192.168.122.202 | error | 1a000511-f17b-4024-b54d-6ae3cf00673a | 19 | 2 | 2014-11-04T04:12:55.000000 | 2014-11-04T04:12:56.000000 |
| cloudcontroller | cloudcontroller | cloudcontroller | cloudcontroller | 192.168.122.202 | error | 1a000511-f17b-4024-b54d-6ae3cf00673a | 19 | 15 | 2014-11-12T06:34:24.000000 | 2014-11-12T06:34:25.000000 |
| cloudcontroller | cloudcontroller | cloudcontroller | cloudcontroller | 192.168.122.202 | error | 1a000511-f17b-4024-b54d-6ae3cf00673a | 19 | 15 | 2014-11-12T06:36:19.000000 | 2014-11-12T06:36:20.000000 |
+-----------------+-----------------+-----------------+-----------------+-----------------+-----------+--------------------------------------+------------+------------+----------------------------+----------------------------+

jichen@cloudcontroller:~$ nova flavor-list
+------+-----------+-----------+------+-----------+---------+-------+-------------+-----------+
| ID | Name | Memory_MB | Disk | Ephemeral | Swap_MB | VCPUs | RXTX_Factor | Is_Public |
+------+-----------+-----------+------+-----------+---------+-------+-------------+-----------+
| 1 | m1.tiny | 512 | 1 | 0 | | 1 | 1.0 | True |
| 100 | m1.test | 1024 | 5 | 0 | | 1 | 1.0 | True |
| 101 | m1.test1 | 512 | 5 | 0 | | 1 | 1.0 | True |
| 1010 | ji.t1 | 512 | 1 | 10 | | 1 | 1.0 | True |
| 1011 | ji.t2 | 512 | 1 | 20 | | 1 | 1.0 | True |
| 2 | m1.small | 2048 | 20 | 0 | | 1 | 1.0 | True |
| 3 | m1.medium | 4096 | 40 | 0 | | 2 | 1.0 | True |
| 4 | m1.large | 8192 | 80 | 0 | | 4 | 1.0 | True |
| 42 | m1.nano | 64 | 0 | 0 | | 1 | 1.0 | True |
| 451 | m1.heat | 512 | 0 | 0 | | 1 | 1.0 | True |
| 5 | m1.xlarge | 16384 | 160 | 0 | | 8 | 1.0 | True |
| 84 | m1.micro | 128 | 0 | 0 | | 1 | 1.0 | True |
| 91 | m2.tiny | 512 | 1 | 0 | | 2 | 1.0 | True |

but my flavor don't have a ID with 19 or 15

[jichenjc (jichenjc)]

maybe it's a microversion update candidate

[Joe Gordon (jogo)]

There isn't enough information in this bug to reproduce it or to resolve it. Can you please add more detail and move this back into new.

[jichenjc (jichenjc)]

take this for example:

| cloudcontroller | cloudcontroller | cloudcontroller | cloudcontroller | 192.168.122.202 | confirmed | cb7c6742-7b7a-44de-ad5a-8570ee520f9e | 2 | 15 | 2014-08-27T01:36:58.000000 | 2014-08-27T01:42:27.000000 |

the id is 2 and 15

however
from this command
jichen@cloudcontroller:~$ nova flavor-list

we can't #15

so the id is not helpful ,actually it's the 'id' not the 'flavorid' which is not helpful to admin
change to flavorid will be hlepful

but it might affect current user ,so need microversion's help

[Daniel Berrange (berrange)]

> take this for example:
>
> | cloudcontroller | cloudcontroller | cloudcontroller | cloudcontroller | 192.168.122.202 | confirmed | cb7c6742-7b7a-44de-ad5a-8570ee520f9e | 2 | 15 | 2014-08-27T01:36:58.000000 | 2014-08-27T01:42:27.000000 |
>
> the id is 2 and 15

What is this data ? What command is this coming from ?

> jichen@cloudcontroller:~$ nova flavor-list
>
> we can't #15
>
> so the id is not helpful ,actually it's the 'id' not the 'flavorid' which is not helpful to admin
> change to flavorid will be hlepful

This is all pretty unintelligible.

I think it would be helpful if you described at a high level what you are trying to achieve wrt migration.

[Robert Collins (lifeless)]

I think they are saying that the flavor.id is returned, not the flavor.flavorid. Seems pretty straightforward to me.

[Robert Collins (lifeless)]

jichenjc what command is getting the migration information for you?

[jichenjc (jichenjc)]

[root@ip9-114-194-247 ~]# nova migration-list
+-------------+-----------+----------------+--------------+---------------+-----------+--------------------------------------+------------+------------+----------------------------+----------------------------+
| Source Node | Dest Node | Source Compute | Dest Compute | Dest Host | Status | Instance UUID | Old Flavor | New Flavor | Created At | Updated At |
+-------------+-----------+----------------+--------------+---------------+-----------+--------------------------------------+------------+------------+----------------------------+----------------------------+

will return the migration info, thanks

[Markus Zoeller (markus_z) (mzoeller)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY