| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2020-03-18 | |||
| 13:01:17 | artom | gibi, thanks for the cleanup :) | |
| 13:02:12 | artom | I would have been even more agressive - like https://review.opendev.org/#/c/525335 is from 2 years ago with no response | |
| 13:02:27 | artom | But I won't tell you how to do your job ;) | |
| 13:03:31 | openstackgerrit | waleed mousa proposed openstack/os-vif master: [Follow Up] OVS DPDK port representors support https://review.opendev.org/705018 | |
| 13:04:29 | luyao | artom: Hi | |
| 13:04:29 | ygk_12345 | hi all | |
| 13:04:40 | ygk_12345 | i have rocky setup. | |
| 13:05:10 | ygk_12345 | when I try to launch an instance on a specific compute node , it is throwing this error in the nova-compute logs | |
| 13:05:12 | ygk_12345 | Failed to retrieve resource provider tree from placement API for UUID ea3af0ff-fb69-449a-b484-5ac722010a1f | |
| 13:07:29 | gibi | artom: you recently asked questions on https://review.opendev.org/#/c/525335 so I allow the author to answer. :) | |
| 13:07:39 | sean-k-mooney | ygk_12345: does the vm launch correctly | |
| 13:08:02 | ygk_12345 | sean-k-mooney no . it is going into error state | |
| 13:08:12 | sean-k-mooney | ygk_12345: i cant recall which release we made placmenert mandatory but have you deployed the placement service | |
| 13:08:38 | ygk_12345 | sean-k-mooney its rocky 18.1.9 branch in openstack ansible | |
| 13:09:08 | sean-k-mooney | did you delete the compute node and recreate it? | |
| 13:09:42 | ygk_12345 | sean-k-mooney i tried upgrading the working rocky setup to stein . it failed and so rolled back to rocky now | |
| 13:09:47 | ygk_12345 | yes | |
| 13:10:02 | ygk_12345 | sean-k-mooney how to delete the compute node ? | |
| 13:10:22 | ygk_12345 | sean-k-mooney i re ran the nova playbook | |
| 13:10:45 | sean-k-mooney | so this is not a nova issue. its and issue with osa and the operation you performed. | |
| 13:11:14 | ygk_12345 | sean-k-mooney so whats the workaround now ? | |
| 13:11:33 | sean-k-mooney | i think we have disucssed this before but if you delete the compute service and you restart the agent without altering the host name of the compute host then it will create a new compute service record in the db with a differnet uuid | |
| 13:12:11 | sean-k-mooney | but that will prevent the the agent form creating the resouce provider with the new uuid as the RP name will still be in use | |
| 13:12:35 | sean-k-mooney | can you validate that by checking if there is a placmenet RP with the hostname? | |
| 13:12:38 | ygk_12345 | sean-k-mooney i have altered the hostname and it created the new record in resource_providers db in nova_api table | |
| 13:12:46 | luyao | artom: If you see my message, could you help look at https://review.opendev.org/#/c/687856/15/nova/compute/manager.py@8336, I change the order of cleanup during post live migration. We do post_live_migration_at_destination first and then cleanup source host in existing code logic, if there are some specific reason ? Or if the order doesn't matter? | |
| 13:12:54 | ygk_12345 | sean-k-mooney how to do that ? | |
| 13:16:52 | artom | gibi, fair enough :) | |
| 13:17:01 | sean-k-mooney | you can use the plamcent openstack client plugin to list the resouce providers and grep for the hostname | |
| 13:17:42 | gibi | artom: ping me next week and I will close out the next patch of reviews including the one you commented :) | |
| 13:17:49 | ygk_12345 | sean-k-mooney is placement included at all in rocky ? | |
| 13:18:05 | artom | luyao, looking... | |
| 13:18:17 | artom | gibi, hehe, ack | |
| 13:18:35 | sean-k-mooney | ygk_12345: it was intoduced in pike maybe earlier | |
| 13:19:02 | sean-k-mooney | ygk_12345: so yes it should be included in rocky | |
| 13:19:42 | luyao | artom: thanks | |
| 13:20:37 | ygk_12345 | sean-k-mooney how to install the placement plugin for the openstack client | |
| 13:21:15 | sean-k-mooney | i think its just "pip install osc-placement" | |
| 13:21:53 | ygk_12345 | sean-k-mooney should I do it in the utility node in openstack ansible ? | |
| 13:21:55 | sean-k-mooney | well "python3 -m pip install --user osc-placement" woudl be more modern way of doing it | |
| 13:21:58 | lyarwood | bauzas: random scheduler question for you, if we fail to schedule an instance and it moves to ERROR can we ever retry launching that instance or can we only delete it? | |
| 13:22:20 | lyarwood | bauzas: working through an issue where failure to schedule an instance with attached volumes leaves these volumes in a reserved state | |
| 13:22:31 | sean-k-mooney | ygk_12345: this really isnt a supprot channel and definetly not for openstack ansible so i dont know. | |
| 13:22:46 | lyarwood | bauzas: but if we are able to schedule and/or go straight to a specific host and then fail the volumes become available | |
| 13:23:17 | lyarwood | I assume we want things to stay reserved *if* we can relaunch the instances somehow | |
| 13:23:38 | ygk_12345 | sean-k-mooney oh ok | |
| 13:35:06 | luyao | stephenfin: Hi, I saw you rechecked my vpmem-live-migration patch. FYI, I submitted a new version, there are a bug in the previous one causing the tempest test failed under mixed-version compute services, I think I addressed it for now, you can look at it if you have time. | |
| 13:37:12 | bauzas | lyarwood: I'm back | |
| 13:37:35 | kashyap | lyarwood: I can't see how your patch is the reason for the 'tempest-integrated-compute' failure | |
| 13:37:42 | kashyap | (Not that you're claiming it :)) | |
| 13:39:19 | lyarwood | kashyap: which one sorry? | |
| 13:39:56 | luyao | artom: I'm afraid I can't response to you promptly in IRC , so I'll appreciate that if you can leave comments under that patch. | |
| 13:39:58 | kashyap | lyarwood: The blockCopy one; sorry - https://zuul.opendev.org/t/openstack/build/1796646647854d128ba128b45d5c7a14 | |
| 13:40:12 | artom | luyao, yeah, that's fine | |
| 13:42:14 | bauzas | lyarwood: to answer your question, you could rebuild I think but not just 'create' again | |
| 13:42:42 | artom | dansmith, when you're about, you don't have to look at the entire patch, but just the https://review.opendev.org/#/c/687856/15/nova/conductor/tasks/live_migrate.py@57 bit, about using compute service versions to judge support for a thing | |
| 13:43:54 | lyarwood | bauzas: so we can't just `nova start $instance` | |
| 13:43:59 | lyarwood | bauzas: we have to rebuild? | |
| 13:44:23 | lyarwood | bauzas: either way, I'd assume that given that's an option the volumes should stay reserved right? | |
| 13:49:21 | bauzas | lyarwood: 'start' recreates the guest XML but doesn't ask for cinder and neutron | |
| 13:49:27 | bauzas | (AFAIR) | |
| 13:50:12 | lyarwood | bauzas: it should update the attachment but it wouldn't recreate it | |
| 13:51:15 | bauzas | yup, this | |
| 13:51:55 | bauzas | either way ,if the instance was set to ERROR on scheduling stage, then the related cell is cell° | |
| 13:51:55 | bauzas | either way ,if the instance was set to ERROR on scheduling stage, then the related cell is cell° | |
| 13:51:59 | bauzas | cell0 sorry | |
| 13:52:09 | bauzas | so you're messed up | |
| 13:52:21 | bauzas | that's why a rebuild or resize is the only option | |
| 13:56:41 | sean-k-mooney | the nova start api action calls power on the virt driver which in the libvirt driver calls hard reboot because reasons | |
| 13:57:24 | sean-k-mooney | so yes it recreates the xml. it might rettrive attachemnt info form cinder but it will not modify the sate of the volume in cinder | |
| 13:57:54 | lyarwood | sean-k-mooney / bauzas ; ack thanks | |
| 13:58:08 | lyarwood | so I'm thinking that either way the volume needs to remain reserved | |
| 13:58:19 | lyarwood | if we ERROR out during scheduling (current behaviour) | |
| 13:58:36 | lyarwood | or if we ERROR out in the virt driver during spawn (currently moves back to available) | |
| 13:58:37 | sean-k-mooney | well if you stop an instance then start it we should not hit the scuduler | |
| 13:58:43 | sean-k-mooney | we dont for a hard reboot | |
| 13:58:59 | lyarwood | right | |
| 13:59:16 | sean-k-mooney | a rebuild need to hit the schduler to assert the new image does not contian metadata that invaldiate the current host | |
| 13:59:26 | sean-k-mooney | but start and reboot dont cause nothing changes | |
| 13:59:38 | lyarwood | right | |
| 13:59:45 | sean-k-mooney | lyarwood: whats the issue you are looking at by the way | |
| 14:01:00 | lyarwood | sean-k-mooney: as above, when we ERROR out during scheduling attached volumes remain in a reserved state (as we don't delete their attachments in cinder), if we fail during spawn the compute layer moves the volume back to available (by deleting the attachments in cinder). | |
| 14:01:20 | nightmare_unreal | hello where can I see list of bugs for openstack CLI client or nova related bugs | |
| 14:01:43 | sean-k-mooney | lyarwood: ah ok | |
| 14:01:48 | lyarwood | sean-k-mooney: so I'm thinking that for the latter we should keep the volume reserved to avoid something or someone else coming along and using it | |
| 14:01:58 | lyarwood | if it isn't multiattach etc etc | |
| 14:02:51 | sean-k-mooney | lyarwood: the later being during spawn when we delete the attachemtn we leave it in a reserved sate | |
| 14:03:20 | lyarwood | sean-k-mooney: when we delete the attachments the volume moves back to an available state | |
| 14:03:37 | lyarwood | sean-k-mooney: I'd like to change this to keep it reserved by not deleting the attachments | |
| 14:04:23 | sean-k-mooney | in the case wehre start fails or boot fails or both | |
| 14:04:42 | sean-k-mooney | for boot it will end up in cell 0 and have host so no attachemts | |
| 14:04:57 | sean-k-mooney | *no host | |
| 14:05:17 | lyarwood | for spawn, so we have a host and a cell already | |
| 14:06:29 | lyarwood | brb | |
| 14:24:31 | sean-k-mooney | nightmare_unreal: nova bugs are here https://bugs.launchpad.net/nova | |
| 14:24:45 | sean-k-mooney | nightmare_unreal: the openstack client uses storyborad | |
| 14:25:52 | sean-k-mooney | so here https://storyboard.openstack.org/#!/project/openstack/python-openstackclient but this is all the releated projects https://storyboard.openstack.org/#!/project_group/80 | |
| 14:26:15 | nightmare_unreal | thanks :) | |
| 14:34:45 | dansmith | artom: your sigh about migration func testing is lack of review I assume? | |
| 14:34:55 | dansmith | I'm sure I'm at least partially to blame there | |