| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-08-03 | |||
| 02:16:58 | Kevin_Zheng | when nova returned instance.flavor_id | |
| 02:17:17 | Kevin_Zheng | horizon can still got the deleted flavor | |
| 02:17:34 | Kevin_Zheng | but when it is in api db | |
| 02:17:46 | Kevin_Zheng | delete is gone forever | |
| 02:17:59 | Kevin_Zheng | so cannot display | |
| 02:18:49 | gmann | i see | |
| 02:18:57 | Kevin_Zheng | another thing is that even we can get the correct flavor name | |
| 02:19:06 | Kevin_Zheng | if we modified the flavor details | |
| 02:19:43 | Kevin_Zheng | the display of the flavor under this name will be incorrect | |
| 02:19:58 | Kevin_Zheng | so I guess maybe showing id is better? | |
| 02:20:16 | Kevin_Zheng | but we don't reply id > 2.47 | |
| 02:20:32 | Kevin_Zheng | maybe we should add it to the current reply?? | |
| 02:20:39 | gmann | Kevin_Zheng, so name should be same in horizon after modification right | |
| 02:20:58 | Kevin_Zheng | it depends, you can also edit name | |
| 02:21:34 | Kevin_Zheng | very complicated usecases | |
| 02:21:54 | gmann | but with id it will be same issue that horizon will get deleted id | |
| 02:22:41 | Kevin_Zheng | yeah, maybe people should come up with a solution, I've posted a maillist | |
| 02:26:14 | gmann | Kevin_Zheng, so when horizon modified flavor(deleted old one). and if someone check instance it shows as flavor-id in instance detail even that is deleted | |
| 02:26:21 | gmann | that is till 2,47 | |
| 02:26:40 | gmann | right? | |
| 02:27:01 | Kevin_Zheng | yeah, thats one option, or we could just display the details | |
| 02:27:14 | Kevin_Zheng | because we already have it | |
| 02:27:28 | gmann | i mean what was behavior till 2,47 | |
| 02:28:19 | Kevin_Zheng | Not available will be displayed | |
| 02:28:23 | gmann | instance use to show old flavor id which is deleted | |
| 02:28:31 | Kevin_Zheng | as we moved flavor to api db | |
| 02:28:36 | gmann | yes | |
| 02:28:39 | Kevin_Zheng | and delete is delete there | |
| 02:28:59 | Kevin_Zheng | horizon could not get the flavor from db using id | |
| 02:30:51 | gmann | yea but GET instance shows the flavor id (<2.47) | |
| 02:31:05 | Kevin_Zheng | yeah, | |
| 02:31:31 | gmann | so instance detail in horizon will have old id | |
| 02:31:41 | Kevin_Zheng | correct | |
| 02:31:56 | gmann | when horizon try to fetch the old flavor ? | |
| 02:32:51 | Kevin_Zheng | yes | |
| 02:33:14 | gmann | i mean why horizon try to get old flavor? | |
| 02:34:09 | Kevin_Zheng | because instance saved the old flavor id | |
| 02:34:23 | Kevin_Zheng | and return it to horizon | |
| 02:34:36 | Kevin_Zheng | horizon use it to show the flavor details | |
| 02:34:53 | gmann | show flavor details in Instance detail tab? | |
| 02:35:10 | Kevin_Zheng | yeah | |
| 02:35:21 | Kevin_Zheng | also the instances list tab | |
| 02:35:48 | gmann | humm | |
| 02:36:13 | gmann | so with >2.47 horizon do not need to do that as instance can give flavor detail | |
| 02:36:20 | Kevin_Zheng | maybe | |
| 02:36:36 | gmann | so 2.47 actually solved the problem ? | |
| 02:36:55 | Kevin_Zheng | yeah it could | |
| 02:37:05 | gmann | i mean just show the what instance return either it exit or deleted | |
| 02:37:25 | Kevin_Zheng | yeah | |
| 02:44:05 | gmann | yea but that will be old stale thing that people would not find such flavor in system as horizon modified it | |
| 02:44:26 | gmann | may be you are asking about disabling this feature is good idea | |
| 02:44:46 | Kevin_Zheng | Yeah, I can think of one usecase of this | |
| 02:45:06 | Kevin_Zheng | since flavor have alot of fields | |
| 02:45:20 | gmann | yea | |
| 02:45:21 | Kevin_Zheng | maybe people want to only change one of the field | |
| 02:45:42 | Kevin_Zheng | so they don't want to create a new one and do all the input | |
| 02:46:27 | Kevin_Zheng | I was thinking, maybe instead of delete-and-create, horizon can provide a copy-and-modify | |
| 02:46:37 | gmann | yea | |
| 02:46:39 | Kevin_Zheng | leave the deleting to user | |
| 02:47:00 | gmann | because flavor id changes and thats problem for other instance operation like resize etc | |
| 02:47:09 | Kevin_Zheng | yeah | |
| 02:47:27 | Kevin_Zheng | and people don't know that editing is actually deleting and creating | |
| 02:48:29 | gmann | true | |
| 02:49:02 | Kevin_Zheng | replies on my maillist post is welcomed :) | |
| 02:52:36 | openstackgerrit | Jackie Truong proposed openstack/nova master: Add trusted_certs to instance_extra https://review.openstack.org/457711 | |
| 02:53:45 | openstackgerrit | Jackie Truong proposed openstack/nova master: Add trusted_certs to Instance object https://review.openstack.org/489408 | |
| 02:58:37 | openstackgerrit | zhangdaolong proposed openstack/nova master: Add debug log for fail to get console https://review.openstack.org/490302 | |
| 03:10:11 | openstackgerrit | zhangdaolong proposed openstack/nova master: Keep the code consistent https://review.openstack.org/490304 | |
| 03:38:22 | openstackgerrit | Tony Breeds proposed openstack/nova master: Testing reno 2.5.0 https://review.openstack.org/490313 | |
| 04:01:36 | openstackgerrit | Tony Breeds proposed openstack/nova master: Testing reno 2.5.0 https://review.openstack.org/490321 | |
| 04:55:12 | openstackgerrit | Jonghan Park proposed openstack/nova master: Network should be distinguished by UUID instead of Name https://review.openstack.org/490332 | |
| 06:07:36 | trinaths | guys! I get this error, Instance failed to spawn: VolumeDeviceNotFound . Do I need cinder volumes mandatory for nova-compute to spawn VMS? | |
| 06:22:49 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Fix getting instance bdms in multiple cells https://review.openstack.org/490340 | |
| 06:40:36 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Enable cold migration with target host(1/2) https://review.openstack.org/408955 | |
| 06:55:44 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Enable cold migration with target host(2/2) https://review.openstack.org/408964 | |
| 07:03:27 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Add parameters in cold migrate action https://review.openstack.org/410042 | |
| 08:17:13 | openstackgerrit | Jacek Tomasiak proposed openstack/nova master: ironic: Use internal API endpoint by default https://review.openstack.org/489537 | |
| 08:35:26 | openstackgerrit | Jacek Tomasiak proposed openstack/nova master: ironic: Use internal API endpoint by default https://review.openstack.org/489537 | |
| 09:13:28 | openstackgerrit | zhangdaolong proposed openstack/nova master: Add debug log for fail to get console https://review.openstack.org/490302 | |
| 09:48:46 | mamandle | alex_xu: bauzas: can you please take a look at https://review.openstack.org/#/c/489848/1 which is a backport for Ocata? Thanks. | |
| 10:24:43 | openstack | Launchpad bug 1708424 in OpenStack Compute (nova) "When a flavor has resource extra_specs disabling all standard fields, nova tries to make a request to the placements API with no resources" [Undecided,New] | |
| 10:24:43 | sambetts | edleafe: Hi, someone testing out Ironic+resource classes accidentally stubbled onto this error, we've put together a bug report for you: https://bugs.launchpad.net/nova/+bug/1708424 | |
| 10:29:02 | openstack | Launchpad bug 1700583 in OpenStack Compute (nova) "No volume Block Device Mapping in assisted snapshot with Quobyte" [Undecided,New] | |
| 10:29:02 | kaisers2 | mriedem: Hi! FYI regarding your email (http://lists.openstack.org/pipermail/openstack-dev/2017-July/120120.html) i found an issue (https://bugs.launchpad.net/devstack/+bug/1700583), took me quite a while to find the connection, so sorry for beeing this late | |
| 10:35:50 | mdbooth | lyarwood: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/ocata+topic:bug/1686116 | |
| 10:36:12 | mdbooth | The code isn't invasive | |
| 10:37:11 | mdbooth | Just putting my tinfoil hat on, trying to think what this would change to an existing instance that was rebooted, for eg | |
| 10:39:11 | mdbooth | disks would have a disk_unit where previously they didn't | |
| 10:43:02 | mdbooth | lyarwood: https://review.openstack.org/#/c/481137/ | |
| 10:43:19 | mdbooth | Disks will have a device address, but only if they've been previously parsed from the domain xml? | |
| 10:44:41 | mdbooth | lyarwood: Anyway, the question was whether it's fit for stable. | |
| 10:44:52 | mdbooth | lyarwood: Is there a specific driver to backport this to stable? | |
| 10:45:01 | robcresswell | sdague: Followed the email chain; my thought on the Horizon "feature" is to gate it behind a setting, disable by default and warning the hell out of it. | |
| 10:45:03 | lyarwood | mdbooth: yeah correct re the question | |
| 10:45:06 | mdbooth | I suspect that it won't break anything. | |
| 10:45:34 | mdbooth | However, if I was of a nervous disposition I wouldn't take it. | |
| 10:45:46 | mdbooth | The code's fine. | |
| 10:46:08 | lyarwood | right, I can't see anything in master that would handle a corner case for active instances | |
| 10:46:25 | lyarwood | so having it in stable should be the same | |
| 10:46:47 | robcresswell | sdague: Referring the edit flavor issue, if that wasnt apparent. I'm not a fan of UI's inventing features that APIs dont support, so I'm on board with getting rid of it. So I'll make the settings changes and deprecate it for Pike. | |