Monday, 2021-07-05

opendevreviewEric Xie proposed openstack/nova master: Add logs when cannot fit numa  https://review.opendev.org/c/openstack/nova/+/79818701:12
*** abhishekk is now known as akekane|home04:52
*** akekane|home is now known as abhishekk04:52
*** bhagyashris_ is now known as bhagyashris|ruck07:40
*** rpittau|afk is now known as rpittau07:45
opendevreviewYongli He proposed openstack/nova master: Smartnic support - cyborg drive  https://review.opendev.org/c/openstack/nova/+/77136208:42
opendevreviewYongli He proposed openstack/nova master: smartnic support - new vnic type  https://review.opendev.org/c/openstack/nova/+/77136308:42
opendevreviewYongli He proposed openstack/nova master: smartnic support - create arqs  https://review.opendev.org/c/openstack/nova/+/75894408:42
opendevreviewYongli He proposed openstack/nova master: smartnic support - build instance with smartnic arqs  https://review.opendev.org/c/openstack/nova/+/79824908:42
opendevreviewYongli He proposed openstack/nova master: smartnic support - cleanup arqs  https://review.opendev.org/c/openstack/nova/+/79805408:43
opendevreviewYongli He proposed openstack/nova master: smartnic support - reject server move and suspend  https://review.opendev.org/c/openstack/nova/+/77991308:43
opendevreviewYongli He proposed openstack/nova master: smartnic support - functional tests  https://review.opendev.org/c/openstack/nova/+/78014708:43
lyarwoodstephenfin / gibi ; https://review.opendev.org/c/openstack/nova/+/720769 - would you mind hitting this today, https://launchpad.net/bugs/1860913 spells out the usecase pretty well.09:04
gibilyarwood: looking09:05
lyarwoodmany thanks09:06
stephenfinsure09:08
*** iurygregory is now known as iury|holiday09:18
*** ralonsoh_ is now known as ralonsoh09:20
gibilyarwood, stephenfin: what was the solution for the failure of test_archive_task_logs functional test ?09:29
stephenfinum...09:29
stephenfingibi: can you give me a bit more context? It's Monday morning :-P09:30
gibiI saw multiple patches failing with https://ef75749a93c952a7bcbb-88cdb958b5e15841b787b658e9835738.ssl.cf5.rackcdn.com/720769/16/check/nova-tox-functional-py39/f1f266b/testr_results.html09:30
gibiand I cloudly recall somebody pinged melwitt about it last week09:30
gibibut I cannot reproduce the issue locally09:30
stephenfinoh, I have no idea. Didn't know there was an issue there09:31
alex_xugibi: I feel smartnic patches are ready for your review https://review.opendev.org/q/topic:%22bp%252Fsriov-smartnic-support%22+(status:open%20OR%20status:merged)09:31
gibialex_xu: thanks. I will try to get to them, but based on how many times I made promise review it without actually getting there I don't want to promise any more. I will try09:32
alex_xugibi: thanks!09:32
gibistephenfin: no worries09:32
alex_xuI think the major logic is on the third and fourth patch09:32
lyarwoodgibi: I think that was me pinging about it09:41
lyarwoodgibi: iirc it suddenly stopped failing09:41
* lyarwood checks09:41
gibistrange09:41
lyarwoodhttps://zuul.opendev.org/t/openstack/builds?job_name=nova-tox-functional-py38&project=openstack%2Fnova&branch=master&pipeline=check09:41
lyarwoodhttps://bugs.launchpad.net/nova/+bug/193451909:41
lyarwoodyeah really odd09:41
lyarwoodI can only assume something was reverted in a dep that fixed it09:42
* lyarwood moves the bug to incomplete09:42
*** bhagyashris_ is now known as bhagyashris|ruck10:08
lyarwoodtest_volume_backed_live_migration is still failing10:14
lyarwoodargh10:14
lyarwoodactually that might be an issue with the change10:15
lyarwoodbecuase https://zuul.opendev.org/t/openstack/builds?job_name=nova-live-migration&project=openstack%2Fnova&branch=master&pipeline=check looks pretty good10:15
lyarwoodhttp://paste.openstack.org/show/807166/ - made some progress with this, it isn't related to the patch AFAICT10:48
* lyarwood heads to #virt10:48
gibilyarwood: good finding11:01
* gibi needs a libvirt debugging / log reading course :)11:01
kashyapgibi: Heh, I once did a bit of it on list:11:02
kashyapgibi: You need to follow the request/response "libvirt-$ID": http://lists.openstack.org/pipermail/openstack-dev/2016-October/105158.html11:03
kashyapEach request and response will have the same libvirt-ID: libvirt-30 (or whatever number) 11:04
kashyaplyarwood: I saw the brief chat on #virt; it's the dreaded "Device or resource busy" problem11:04
kashyapIt is my list of top two "most notorious libvirt errors"11:04
lyarwoodkinda11:05
lyarwoodthat's causing libvirtd to lockup11:05
lyarwoodthe migration is in a different thread11:05
lyarwoodand the dest times out before the src11:05
lyarwoodbut the src then continues11:05
lyarwoodthat's a separate behavioural issue in libvirtd tbh11:05
kashyapMe nods11:06
kashyapThere's also the SIGTERM / SIGKILL dance.  Often times only killing the instance and restarting seems to be the "solution"11:06
kashyap(Aside: if you're wondering what is the other error in my top-2 list, it's the "cannot acquire state change lock")11:07
gibikashyap: thank I will read that11:11
opendevreviewMerged openstack/nova-specs master: [template]suggest work item ordering  https://review.opendev.org/c/openstack/nova-specs/+/79319712:05
sean-k-mooneybauzas: im +2 on https://review.opendev.org/c/openstack/nova-specs/+/792796 by the way but held off +w to see if you want to adress teh nits in a follow up patch or if you wanted to quickly respin12:06
bauzassean-k-mooney: ack, will quickly look (was on PTO on Friday)12:17
*** tbachman is now known as Guest154812:34
alexe9191Goodday everyone :) 14:46
alexe9191I was wondering if anyone has information on this blueprint? https://blueprints.launchpad.net/nova/+spec/detach-boot-volume 14:46
alexe9191I see that it is waiting for approval since train and I was wondering if there are any plans to release it anytime soon ?14:46
sean-k-mooneyi think the people proposing it did not complete it14:46
alexe9191too bad14:47
sean-k-mooneyhttps://review.opendev.org/q/topic:%22bp%252Fdetach-boot-volume%22+(status:open%20OR%20status:merged)14:48
gibiyepp it seems it is simply stalled out https://review.opendev.org/c/openstack/nova/+/623981/14:48
sean-k-mooneyhttps://review.opendev.org/q/topic:%2522bp/detach-boot-volume%2522+14:48
sean-k-mooneyso the most recent code is abandoned14:48
sean-k-mooneyalexe9191: it could be picked back up14:49
sean-k-mooneyi dont think it stalled out because of design reasons14:49
sean-k-mooneymatt's -1 was because we did not need to bump the object verion and the is_multi_attach is not implemted correctly14:51
sean-k-mooneyhttps://review.opendev.org/c/openstack/nova/+/623981/24/nova/objects/block_device.py14:51
alexe9191Abandoned meaning no one is working on it, or it won't be implemented for other reasons?14:52
sean-k-mooneyalexe9191: no one is working on it14:53
sean-k-mooneyit can be repoposed and implemented if people still want it and have time to work on it14:53
opendevreviewMerged openstack/nova-specs master: Re-propose "CPU selection with hypervisor consideration"  https://review.opendev.org/c/openstack/nova-specs/+/79909616:11
opendevreviewLee Yarwood proposed openstack/nova master: WIP/DNM - block_device: Use initialize APIs to refresh when reported as idempotent  https://review.opendev.org/c/openstack/nova/+/72076916:18
*** rpittau is now known as rpittau|afk16:20
opendevreviewStephen Finucane proposed openstack/nova master: db: Use module-level imports for sqlalchemy (for real)  https://review.opendev.org/c/openstack/nova/+/79651916:26
opendevreviewStephen Finucane proposed openstack/nova master: db: Move db.sqalchemy.migration to db.migration  https://review.opendev.org/c/openstack/nova/+/79951816:26
opendevreviewStephen Finucane proposed openstack/nova master: db: Move main DB migrations  https://review.opendev.org/c/openstack/nova/+/79951916:26
opendevreviewStephen Finucane proposed openstack/nova master: db: Move 'sqlalchemy.types' up a directory  https://review.opendev.org/c/openstack/nova/+/79952016:26
opendevreviewStephen Finucane proposed openstack/nova master: db: Remove constant aliases from 'nova.db.api'  https://review.opendev.org/c/openstack/nova/+/79952116:26
opendevreviewStephen Finucane proposed openstack/nova master: db: Drop support for experimental concurrency  https://review.opendev.org/c/openstack/nova/+/79952216:26
opendevreviewStephen Finucane proposed openstack/nova master: db: Register database config options ourselves  https://review.opendev.org/c/openstack/nova/+/79952316:26
opendevreviewStephen Finucane proposed openstack/nova master: db: Unify 'nova.db.api', 'nova.db.sqlalchemy.api'  https://review.opendev.org/c/openstack/nova/+/79952416:26
opendevreviewStephen Finucane proposed openstack/nova master: db: Move remaining 'nova.db.sqlalchemy' modules  https://review.opendev.org/c/openstack/nova/+/79952516:26
opendevreviewStephen Finucane proposed openstack/nova master: db: Post reshuffle cleanup  https://review.opendev.org/c/openstack/nova/+/79952616:26
opendevreviewStephen Finucane proposed openstack/nova master: db: Add initial alembic migration for main DB  https://review.opendev.org/c/openstack/nova/+/79952716:26
opendevreviewStephen Finucane proposed openstack/nova master: db: Add initial alembic migration for API DB  https://review.opendev.org/c/openstack/nova/+/79952816:26
opendevreviewStephen Finucane proposed openstack/nova master: db: Trivial style changes  https://review.opendev.org/c/openstack/nova/+/79952916:26
opendevreviewStephen Finucane proposed openstack/nova master: WIP: db: Integrate alembic  https://review.opendev.org/c/openstack/nova/+/79953016:26
opendevreviewGhanshyam proposed openstack/placement master: Fix oslo policy DeprecatedRule warnings  https://review.opendev.org/c/openstack/placement/+/79941816:28
stephenfindansmith: If you have a bit of spare time, I'd appreciate some eyes on the last one of those patches ^ I can't quite figure out why the 'CellDatabases' fixtures is failing but it is :-\16:29
sean-k-mooneygibi: how do you feel about https://review.opendev.org/c/openstack/nova-specs/+/791047/2/specs/xena/approved/pci-device-tracking-in-placement.rst#152 doing the pci inventory reservation via moving the instance claim to the conductor17:12
sean-k-mooneystephenfin: ^ also of interest to you17:12
sean-k-mooneywe have talked about moving the instance claim to the conductor for years and it will simplfy pci in placment as well as resolve some other numa issues17:13
opendevreviewElod Illes proposed openstack/nova stable/pike: Use subqueryload() instead of joinedload() for (system_)metadata  https://review.opendev.org/c/openstack/nova/+/79953317:24
noonedeadpunkhey there! We just relesed W and switched back to tracking master branch and found our upgrade jobs failing on Nova, after upgrade from stable/wallaby to master17:36
noonedeadpunkwith smth like http://paste.openstack.org/show/807170/17:37
noonedeadpunkand looking at https://opendev.org/openstack/nova/src/branch/master/nova/objects/service.py#L207-L211 it makes me wonder wtf is going on here :)17:38
lyarwoodnoonedeadpunk: https://github.com/openstack/nova/blob/66fb0ecb5a867c054ab266aadcc06a940967abd4/nova/objects/service.py#L33-L34 looks like it is 53 on stable/victoria at least18:03
lyarwoodthat would make sense given your error18:03
noonedeadpunkah, ok, yes18:03
noonedeadpunknow it does :)18:04
noonedeadpunklyarwood: so, eventually now jumping through releases is not going to work, right? So if I'd love to do V->X upgrade, it's not gonna work (like T->V did nicely)18:04
lyarwoodI don't get why the alias is 52 in master however18:04
lyarwoodnoonedeadpunk: we have only ever supported N to N+118:05
noonedeadpunkbut toher then that never failed explicitly :D18:05
lyarwoodnoonedeadpunk: and even with things like FFU downstream we take everything down at N and bring everything back up at N+318:05
lyarwoodnoonedeadpunk: yeah that was more luck than anything, there was no test coverage of anything other than N to N+118:06
noonedeadpunkI think I found some mistake and in CI we were upgrading from V to master, which made this part fail18:06
noonedeadpunkyeah, we also test only N to N+118:06
* lyarwood heads off for dinner \o18:07
noonedeadpunkbtw, maybe you have some idea, would computes in N+1 work with N API? Ie if you upgrade computes first?18:07
lyarwoodYes that should work18:22
lyarwoodyou just need to pin your computes to the older rpc versions18:23
lyarwoodbut it isn't the way we test upgrades18:23
sean-k-mooneynoonedeadpunk: actully it wont work18:24
sean-k-mooneyyou have to upgrade the contoler first18:24
sean-k-mooneyso you always have to upgrade the api, conductor and schduler together18:25
sean-k-mooneyand they must be upgraded to N+1 before you upgade any comnputes to n+118:25
sean-k-mooneywhile you could technially pin the rpc version and you might be able to get them to work it would be unsuppoted upstream and downstream18:26
sean-k-mooneythe compute always assume that the contoler are at least teh same version18:26

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!