| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-01-29 | |||
| 12:47:44 | openstackgerrit | Stephen Finucane proposed openstack/nova master: mypy: Add type annotations to 'nova.pci' https://review.opendev.org/c/openstack/nova/+/676209 | |
| 12:47:45 | openstackgerrit | Stephen Finucane proposed openstack/nova master: mypy: Add type annotations to top-level modules https://review.opendev.org/c/openstack/nova/+/705658 | |
| 12:47:45 | openstackgerrit | Stephen Finucane proposed openstack/nova master: mypy: Add nova.cmd, nova.conf, nova.console https://review.opendev.org/c/openstack/nova/+/705657 | |
| 12:47:46 | openstackgerrit | Stephen Finucane proposed openstack/nova master: WIP: Expand type hints for nova.block_device https://review.opendev.org/c/openstack/nova/+/742170 | |
| 12:47:46 | openstackgerrit | Stephen Finucane proposed openstack/nova master: trivial: Clean manager.Manager, service.Service signatures https://review.opendev.org/c/openstack/nova/+/764806 | |
| 12:54:14 | openstackgerrit | Merged openstack/nova master: Enable mypy on scheduler/utils.py https://review.opendev.org/c/openstack/nova/+/769942 | |
| 13:16:54 | kashyap | gibi: Nice split of your wait-for-libvirt-events patches ... it's easier to review | |
| 13:40:26 | gibi | thanks | |
| 14:26:42 | kashyap | And thanks for updating the bug metadata for me | |
| 14:29:08 | gibi | no problem. I hope at some point the automatic update will work again with the new gerrit | |
| 15:54:46 | stephenfin | gibi, bauzas: This patch has been around for a while. If you've a few minutes spare next week, could you chuck it onto your review queues? https://review.opendev.org/c/openstack/nova/+/741663/ | |
| 15:54:55 | stephenfin | The other ones would be nice too, but that would be a good start :) | |
| 15:55:20 | gibi | ohh notifier, nice | |
| 15:55:24 | gibi | I will look at it | |
| 15:55:33 | stephenfin | thanks :) | |
| 15:59:01 | bauzas | stephenfin: ack, will try | |
| 16:03:15 | brtknr | what are ccommon reasons for nova and cinder states going out of sync? | |
| 16:13:39 | sean-k-mooney | sometimes tokens can expire cause the update of cinder to not happen correctly | |
| 16:13:51 | sean-k-mooney | service_tokens solves that problem | |
| 16:14:14 | sean-k-mooney | the other common case is where you hit a bug during a move operation or in the revert of a move operation | |
| 16:15:44 | sean-k-mooney | where move opartion bugs are not caused by token issues tempory entwork issue with rabbitmq or the cinder api can cause reverts or updates to be lost which if they are not retried can lead to them being out of sync | |
| 16:16:10 | sean-k-mooney | i think we retry cinder calls up to 3 times by default to mitigate the tempory api outage case | |
| 16:17:50 | sean-k-mooney | stephenfin: by the way im not worried about delineation i just find [libvirt]/virt_type more pleaseing to read then [libvirt]virt_type | |
| 16:18:07 | stephenfin | what about '[libvirt] virt_type' | |
| 16:18:31 | sean-k-mooney | that i could be ok with if it was in quotes | |
| 16:18:46 | sean-k-mooney | btu in a sentance without the qutoes or backticks i think that coudl be more confusin | |
| 16:18:56 | stephenfin | That's fair | |
| 16:19:03 | sean-k-mooney | so [libvirt] virt_type is a littel confusing | |
| 16:19:31 | stephenfin | The one good thing that did come out of that discussion is that I spotted a lot of examples in the docs that were not using the ':oslo.config:option:' role | |
| 16:19:36 | sean-k-mooney | but '[libvirt] virt_type' is fine | |
| 16:19:37 | stephenfin | So I'm going to fix those | |
| 16:20:12 | sean-k-mooney | ya so one thing about that though is we cant use that in the release notes right | |
| 16:20:22 | stephenfin | no, we can't | |
| 16:20:23 | sean-k-mooney | so i have always used the / there | |
| 16:20:30 | sean-k-mooney | and in specs | |
| 16:21:04 | sean-k-mooney | i agree though were we can use the olso way we proably should | |
| 16:21:30 | stephenfin | for sure | |
| 16:21:31 | sean-k-mooney | on a different topic | |
| 16:21:39 | sean-k-mooney | have we remvoed libvirt/xen support | |
| 16:21:43 | sean-k-mooney | or just xenapi | |
| 16:21:46 | stephenfin | we have, yes | |
| 16:21:50 | stephenfin | that merged last week | |
| 16:21:57 | stephenfin | libvirt/UML is gone too | |
| 16:21:59 | sean-k-mooney | ah ok that was my quetion on https://review.opendev.org/c/openstack/nova/+/772928 | |
| 16:22:06 | sean-k-mooney | cool ill upgrate to a +1 then | |
| 16:22:18 | stephenfin | Yup, the Change-Id I linked is the patch that removed it | |
| 16:22:26 | sean-k-mooney | oh you called it out in the commit message missed that | |
| 16:22:33 | stephenfin | Yup :-) | |
| 16:23:14 | sean-k-mooney | if a commit message is really short i dont always read them for short patchs | |
| 16:23:28 | sean-k-mooney | if the patch is anyway long i do but in this case it would have helped | |
| 16:23:47 | stephenfin | you mean you don't read the literary marvels that are my commit messages | |
| 16:23:50 | stephenfin | I'm disappointed :P | |
| 16:24:44 | sean-k-mooney | stephenfin: if you right an easy in them i alwasy do | |
| 16:25:00 | sean-k-mooney | but if its 4 lines long for a 32 line patch not normally | |
| 16:25:39 | sean-k-mooney | ill try and take a look at your mypy stuff next week by the way | |
| 16:26:00 | sean-k-mooney | but dont have time to do it today | |
| 16:26:28 | stephenfin | Cool. It's low priority nice-to-have stuff | |
| 16:26:32 | stephenfin | Nothing more | |
| 16:27:38 | sean-k-mooney | ... grenade is failing on https://review.opendev.org/c/openstack/nova/+/602432/ again | |
| 16:28:20 | sean-k-mooney | i said i was not going to work on that if it was not merged by the end of the year, i should have stuck to that | |
| 16:28:28 | sean-k-mooney | but its important | |
| 16:28:30 | openstackgerrit | Balazs Gibizer proposed openstack/nova stable/ussuri: Reproduce bug 1896463 in func env https://review.opendev.org/c/openstack/nova/+/770768 | |
| 16:28:33 | openstack | bug 1896463 in OpenStack Compute (nova) ussuri "evacuation failed: Port update failed : Unable to correlate PCI slot " [Low,In progress] https://launchpad.net/bugs/1896463 - Assigned to Balazs Gibizer (balazs-gibizer) | |
| 16:29:01 | sean-k-mooney | gibi: on nice :) | |
| 16:29:13 | sean-k-mooney | oh that the back port | |
| 16:29:28 | gibi | yepp, I needed to fix it as there was missing deps in ussuri | |
| 16:29:56 | openstackgerrit | Balazs Gibizer proposed openstack/nova stable/ussuri: Set instance host and drop migration under lock https://review.opendev.org/c/openstack/nova/+/770769 | |
| 16:30:37 | sean-k-mooney | im pretty sure we had a customer hit that not so long ago | |
| 16:31:32 | sean-k-mooney | ah yes this https://bugzilla.redhat.com/show_bug.cgi?id=1852110 | |
| 16:31:33 | openstack | bugzilla.redhat.com bug 1852110 in openstack-nova "nova host-evacuation returns erroneous pci addresses and an error: Unable to correlate PCI slot" [High,New] - Assigned to smooney | |
| 16:32:29 | sean-k-mooney | gibi: are you planning to backport that to train out of interest? | |
| 16:32:37 | gibi | sean-k-mooney: cool, it is always nice to know that I helped some real customer | |
| 16:32:40 | gibi | sean-k-mooney: sure | |
| 16:33:03 | gibi | sean-k-mooney: I will propose the train backport when the ussuri one lands | |
| 16:33:53 | sean-k-mooney | thanks that will pull it in ot osp 16 for us. this is agains queesn downstream but not sure we were going to take it back that far | |
| 16:34:13 | sean-k-mooney | train shoudl close this for many of our customers | |
| 16:35:49 | gibi | yeah, my company using pike, train (victoria in the works). I might do the backport til pike if it is not too hard | |
| 16:36:19 | sean-k-mooney | hum our eol for queens is this year but our extended life support is untile 2023 so ya i think if you dont i proably shoudl | |
| 16:36:55 | sean-k-mooney | its a small enough change that it proably worth it to prement suprot ticket as a result of not having it | |
| 16:38:15 | gibi | the change is pretty OK, I affraid that at some point the func reproduce will break in a horrible way | |
| 16:38:52 | sean-k-mooney | ya we have a habbit of rewriting the func tests every cycle | |
| 16:39:10 | sean-k-mooney | they are getting better and better but the more you go back the more likely they break | |
| 16:39:53 | gibi | it is the price of progress | |
| 16:48:59 | openstackgerrit | Balazs Gibizer proposed openstack/nova stable/ussuri: Warn when starting services with older than N-1 computes https://review.opendev.org/c/openstack/nova/+/770764 | |
| 16:49:00 | openstackgerrit | Balazs Gibizer proposed openstack/nova stable/ussuri: Add upgrade check about old computes https://review.opendev.org/c/openstack/nova/+/770765 | |
| 16:57:29 | kashyap | sean-k-mooney: Can I do a 'recheck' for a specific job, please remind me again? | |
| 16:58:42 | stephenfin | kashyap: no | |
| 16:58:51 | stephenfin | rechecks are all or nothing | |
| 16:59:29 | sean-k-mooney | kashyap: if its third party you can normlaly recheck those cis seperatly | |
| 16:59:41 | sean-k-mooney | but no we dont support that because of the green check policy | |
| 17:00:00 | sean-k-mooney | its too easy to allow broken code to merge if you can do it for indivigual jobs | |
| 17:00:49 | sean-k-mooney | we used to have reverify to just rerun the gate pipeline seperate to check and we remove it for that reason | |
| 17:02:09 | kashyap | stephenfin: sean-k-mooney: Yeah, fair enough | |
| 17:04:32 | sean-k-mooney | kashyap: is a speicifc job failing consitently? | |
| 17:04:50 | sean-k-mooney | kashyap: i think lee/gibi fixed something related to nova-next or nova-lvm recently | |
| 17:04:54 | kashyap | Nah; just a Ceph timed-out for the first time | |
| 17:05:01 | kashyap | s/Ceph/Ceph job/ | |
| 17:05:01 | sean-k-mooney | ah ok | |
| 17:08:24 | kashyap | Have a good weekend! | |
| 17:08:35 | sean-k-mooney | same o/ | |