Thursday, 2023-01-26

sean-k-mooneygibi: bauzas  if you could take a look at this in ye're morning or melwitt if your around https://review.opendev.org/c/openstack/nova/+/86732400:33
melwittsean-k-mooney: these options don't follow how [workarounds] is supposed to be a False/True do this or don't thing :/  but I see why it's being done00:43
sean-k-mooneyi dont wnat to put them in the libvirt section as the workaround they are extending was ment to be deleted eventually00:44
sean-k-mooneyand when you use it it "taints" the domain00:44
sean-k-mooneyso at least downstream we had to get approval form our virt team to have this not "viod the warrenty" when it comes to support00:45
sean-k-mooneyi would be fine with moving them to the libvirt section if the libvirt api we asked for was actully added to libvirt00:46
sean-k-mooneywe ask for a top level api to do the exact same thing that did not mark the domain as tainted00:46
sean-k-mooneyso if that ever becomes a thing i would be happy to move the optiosn to the libvirt section00:46
melwittyeah, I saw you mentioned that in the comments. I understand why but it is kinda weird the concept of fine-tuning [workarounds] and I hope that's not going to become a thing00:47
sean-k-mooneyyou are right about it not just being a bool however. it is still guarded by one however00:47
sean-k-mooneythe thing its most similar too is the interval and retires we have for volume detach00:48
melwittyeah, it's clear it's not a thing that we want to be permanent and why it wouldn't go into the normal configs00:48
sean-k-mooneyi did consider just suggesting hardcoding to 3 with a longer interval00:49
sean-k-mooneybut they already had the config option when i review for the interval00:49
sean-k-mooneyso i kind fo didnt wnat to have anouther patch tweeking this again later00:50
sean-k-mooneyhttps://docs.openstack.org/nova/latest/configuration/config.html#libvirt.device_detach_attempts and https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.device_detach_timeout are the detach/attach options we added that are kind of like it00:51
melwittyeah, would've been ideal to hardcode it but if it's that fiddly then I see why we wouldn't want to have to do future tweaks to it00:51
sean-k-mooneyit kind of sucks that the workaround is needed but ya i expected when we added the orgianal workaround ot not need to do more then one addtional GARP00:52
sean-k-mooneyqemu is already doing 3 before we do anything00:53
melwittack, I don't think the concept is itself weird, it's that you get a lot of fine-grained tuning for your one workaround 😆 I'm not suggesting blocking it but just saying it looks quite odd to me00:53
sean-k-mooneyi agree on the odd but its pargmatic00:53
sean-k-mooneyits kind of like shouting at the network to say hay i really reallly really am over here now00:54
melwittlol :)00:54
sean-k-mooneyanyway its like 1am for me so im going to sleep came onlien to check something breilfy and got distracted with geting my email inbox to 000:55
melwittk g'night! o/00:56
sean-k-mooneyo/00:56
*** blarnath is now known as d34dh0r5306:37
tobias-urdineu people might start their day now :) please have a look at getting a release for the CVE out https://review.opendev.org/c/openstack/releases/+/87180207:57
fricklergibi: bauzas: sean-k-mooney: ^^ I kind of agree with tobias-urdin that there is a bit of urgency behind this. not sure if release team could skip ptl approval in this case, though?08:43
kashyapIs it just me or the "tempest-integrated-compute" is timing out often for others too?08:43
bauzasfrickler: I'm here08:44
bauzasfrickler: we said we were trying to also merge another CVE fix before we release this 08:44
bauzasok, the other cve bug is fixed down to xena, so yeah, we can have releases08:50
* bauzas will look at the change08:50
fricklerthat other CVE was https://review.opendev.org/c/openstack/nova/+/859315, right?08:56
bauzasyup, just checked, reviewing now the releases patch09:04
bauzasgibi: frickler: I was torn with the proposed semver of https://review.opendev.org/c/openstack/releases/+/871802 which was doing .y releases but I can live with that09:09
bauzastobias-urdin: ^ anything in particular you had in mind when you did set the releases for a .y bump ?09:10
bauzasthe fact that it was exposing a new conf knob, I guess ?09:10
gibiI'm fine with the minor bump09:14
bauzasthat seems a bit agressive but thinking out more, that means that distros have to adapt their toolings if they wanna set the new conf knob09:15
bauzasso yeah a .y bump seems ok09:15
bauzaseven if semantically, we're sending a wrong signal09:15
gibiwe are removing functionality with a knob by default so I'm OK to y bump it09:17
gibiI double checked it seems both cve is in the release (the vnit_type on was in zed when it was master)09:17
gibiso I think we are good to go09:18
tobias-urdini pretty much followed cinder that bumped minor, I guess it wouldn't hurt indicating to operations that a minor version that should be upgraded to because of CVE09:20
tobias-urdinbut yeah we can change if required, just wanted to make it a priority to release it so downstream can start building stuff new versions as well09:20
bauzasgibi: yeah, checked the other CVE, was my main original driver for the check09:20
bauzastobias-urdin: no worries, as I said, I can live with that09:21
gibinext is stable/wallaby but that needs the tempest pin first. https://review.opendev.org/q/topic:wallaby-pin-tempest09:21
bauzasin theory a CVE fix doesn't require a y versioning but meh09:21
tobias-urdinbauzas: ack, thanks, i will keep that in mind for the future09:21
bauzasgibi: correct, I +2/+Wd a patch this morning09:21
bauzastobias-urdin: np, not anyone needs to know anything :) but if you wanna know more about semver, this is the reference page https://docs.openstack.org/pbr/latest/user/semver.html09:22
bauzasgibi: do you know if gmann did the tempest patch ?09:23
bauzasI can check, I just didn't had the time yet09:23
gibibauzas: here is the tempest pin series https://review.opendev.org/q/topic:wallaby-pin-tempest it needs love09:23
bauzasI can surely provide love09:23
gibithe DNM test patches are failing09:23
bauzasthen I guess the love has to be on finding why the DNM patches are failing09:24
bauzaslovely09:24
bauzasthat's just 12 hours I haven't looked at zuul files09:24
* bauzas grabs a coffee and steps into it09:25
bauzasmmm09:48
bauzasgibi: does those skipttest exceptions in tempest look correct to you ?09:48
bauzas2023-01-26 01:06:13.455899 | controller |     unittest2.case.SkipTest: Identity api v2 is not enabled09:48
bauzasI have seen gmann rechecking on such errors09:48
bauzashttps://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_0a4/871782/2/check/tempest-full-py3/0a42465/job-output.txt09:49
gibiit does not look good, but maybe gmann rechecked on it as he changed one of the depends-ons09:49
bauzasI just asked for a recheck09:50
bauzason the devstack patch09:50
bauzasanyway, the changes themselves on both tempest and devstack seem logic to me09:51
gibiwe will see09:51
bauzasso I guess this is just a transient issue09:51
bauzasat least keystone was running 09:52
sahido/ sean-k-mooney, bauzas I have noticed your new comments09:53
sahidworking on it !09:53
sahidthanks09:53
bauzassahid: thanks 09:54
bauzassahid: ping me when you're done with those, and I'll rereview09:54
sean-k-mooney[m]the rpc pin case is not something i orginally tought of but i dont think its a large change to just make sure we dont retrun a 500 from the api and add a test for that so hopefully it wont take too much to adress that09:55
bauzassahid: to clarify, sorry but you don't need to change the RPC client, just make sure that on the API you can verify it09:55
sean-k-mooney[m]yep so add a functional test that pins to 6.009:56
sean-k-mooney[m]use the new microversion09:56
sean-k-mooney[m]and assert an excption is raised09:56
sean-k-mooney[m]ideally it should be a 40909:56
sean-k-mooney[m]the same as when the compute is not upgraded09:57
sean-k-mooney[m]you should not expose the crrent RPC pin in the excption09:57
sean-k-mooney[m]just that the could does not meet the requirements for the new microversion and you should use the old  one like the other exception09:58
sean-k-mooney[m]bauzas actully is there any reason not to use the same excpetion here as in the api when the compute service is to low09:59
bauzasgood question10:00
bauzasproblem is, evacuation is defined by policy, right?10:00
sean-k-mooney[m]i guess its and admin api and they might want to know but if they manually pinned. perhapse its diffent admins that do upgrade vs day to day10:00
sean-k-mooney[m]well all apis are controlable by policy10:01
bauzasso you can change the policy to have evacuation (without a host param) be supported for endusers10:01
bauzasif so, we could return something like 'sorry, compute service is too low'10:01
sean-k-mooney[m]you could10:01
bauzasI don't know whether it would be a problem for our operators then10:01
kashyapThis timeout is blocking a couple of patches.  /me is trying to find where exactly is the time_out -- https://zuul.opendev.org/t/openstack/build/453f991eeeb34498b132eb84de3301db/logs10:01
sean-k-mooney[m]sound like just a slow node to be honest10:02
sean-k-mooney[m]and that job might be hitting up agagisnt the timeout anyway but lests see what the normal runtime is10:03
kashyapSo only a full recheck is the only option? :(10:03
kashyap(Already did it once)10:03
sean-k-mooney[m]normally 90 mins or so10:03
kashyapsean-k-mooney[m]: For the full recheck?10:03
sean-k-mooney[m]that job normally takes 90 mins10:04
sean-k-mooney[m]https://zuul.opendev.org/t/openstack/builds?job_name=tempest-integrated-compute&project=openstack/nova10:04
sean-k-mooney[m]there have been 5 time outs in the last 300 runs of that job10:05
sean-k-mooney[m]the 3 time outs are form 4 providers so i dont really see any corralation10:10
sean-k-mooney[m]it would be good to see if there is anything odd in the devstack or tempet runs10:10
sean-k-mooney[m]but something took more time then normal10:10
sean-k-mooney[m]so yes a recheck is the way to proceed but it would be good to see if say a lot of swap was used or an image/pacakge download was slow10:11
sean-k-mooney[m]looking at a passing run vs failing devstack too ~900 seconds vs ~120010:18
sean-k-mooney[m]its seams to be pretty even across apt install pip install and osc10:19
sean-k-mooney[m]so i think this is diskio or just general cpu/disk/net performace related10:19
sean-k-mooney[m]if the devstack install is 33%  slower the tempest execation will likely be similarly reduced in perfromace10:20
sean-k-mooney[m]and a normal run is at 75% of the build limit so it cant really tollerate that much of a slow down10:20
sahidbauzas, sean-k-mooney[m] humm i may missing somethinhg, this is not what you are looking for? https://review.opendev.org/c/openstack/nova/+/858384/34/nova/tests/unit/api/openstack/compute/test_evacuate.py#43110:26
sahidthat is when using microversion 2.95 with a hosts that are not fully upgraded10:27
sean-k-mooney[m]no10:27
sean-k-mooney[m]that is pininng the min compute service version10:27
sean-k-mooney[m]we were talking about the rpc version pin10:27
sean-k-mooney[m]the ones you pin in https://docs.openstack.org/nova/latest/configuration/config.html#upgrade-levels10:28
sean-k-mooney[m]so [upgrade_levels]/compute=6.010:29
bauzassahid: the missing unittest I was referring was to verify that you return an exception if you set the parameter and call a old compute 10:30
bauzassahid: for the functest in the other change (the microversion one), yeah, what sean-k-mooney said10:31
sahidbauzas: this part? https://review.opendev.org/c/openstack/nova/+/858383/25/nova/compute/manager.py#383110:32
bauzassahid: no sorry10:33
bauzassec10:33
bauzassahid: in https://review.opendev.org/c/openstack/nova/+/858383/25/nova/compute/rpcapi.py#110810:33
bauzassahid: you return an exception10:33
bauzasand I'm eventually OK with it (sorry for the comments)10:34
bauzassahid: butn10:34
bauzassahid: I don't see any unittests for verifying the RPC call10:36
sahidyes good point10:36
bauzasand we also need to have unittests for the conductor RPC API, unfortunately :(10:37
bauzassahid: sec, will find you where we have unittests for both10:37
bauzassahid: one example of a simple unittest for testing it https://github.com/openstack/nova/blob/master/nova/tests/unit/conductor/test_conductor.py#L4734-L475210:42
bauzasgosh, our tests are so horrible to read :(10:43
bauzashttps://github.com/openstack/nova/blob/master/nova/tests/unit/conductor/test_conductor.py#L4754-L4788 are also good examples10:43
bauzasjust add two checks there and I'm all good (for the conductor API)10:43
bauzas(even if we apparently missed the other version checks...)10:43
sahidworking on it! thank for you help guys10:44
bauzassahid: for the compute RPC API, here is the existing test https://github.com/openstack/nova/blob/master/nova/tests/unit/compute/test_rpcapi.py#L883-L91610:45
bauzasHTH10:45
bauzassahid: np, you're next in my review queue once you're all set10:45
kashyapsean-k-mooney[m]: Sorry for my delay, just reading back the scroll of your analysis10:51
sean-k-mooneytl;dr the io on those nodes that timeed out looks like its about 33% slower then normal. we are normally at 75% of the timeout so we dont have the headroom in that case10:54
sean-k-mooneygibi: bauzas  can we land gmann's placement service role patch https://review.opendev.org/c/openstack/placement/+/86561811:09
opendevreviewMerged openstack/nova master: Handle InstanceInvalidState exception  https://review.opendev.org/c/openstack/nova/+/86173812:41
kashyapsean-k-mooney: Thanks for the summary.  It's nearly 2-ish hours, and still no sign of a vote - https://review.opendev.org/c/openstack/nova/+/87079413:15
sean-k-mooneyits in gate13:16
sean-k-mooneyits been runing for 1hr 46mins13:16
sean-k-mooneyand tempest-integrated-compute passed already13:17
sean-k-mooneyyou can watch it here if you like https://zuul.openstack.org/status#87079413:17
kashyapsean-k-mooney: Thank you :)13:21
ierdemHi, when I try to cold migrate VMs via cli by specifying destination host, it throws an exception after first migrate "No valid host was found" -no more details, just this message-, but destination host has enough resource. Does nova-scheduler cause this? If is, how can I force it to migrate more than one VMs to the same host? Thanks for all your assistance. (I have kolla-ansible stein-eol)13:33
bauzasgmann: sean-k-mooney: dansmith: sorry, but maybe I'm confused but I thought system readers can scope resources of a deployment. If so, why are we returning HTTP403 on https://review.opendev.org/c/openstack/placement/+/865618 ?13:35
* bauzas reads and rereads https://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html#system-reader and this appears to me Alice should know which resource providers exist, etc.13:36
bauzas(Alice in the spec, obviously)13:36
kashyap(Third time lucky, the job indeed passed)13:37
kashyap(We'll see if everythig else succeeds.)13:38
bauzasoh wait13:38
bauzas"Alice can list or retrieve specific endpoints. Alice cannot do any project specific operations since her authorization is limited to the deployment system."13:38
bauzasincluding list, IIRC13:38
sean-k-mooneybauzas: we are remvoing system reader form the placment polices13:43
sean-k-mooneyfor most project we are geting rid fo scope entirly based on operator feedback in yoga?13:44
* bauzas is lost in translation13:45
bauzasbut okay13:46
bauzasI can understand we restrict the roles then13:46
* bauzas wishes we have some docs about roles which isn't a rocky spec13:46
bauzasand which can be updated as long as we implement the features13:46
opendevreviewMerged openstack/nova master: libvirt: At start-up rework compareCPU() usage with a workaround  https://review.opendev.org/c/openstack/nova/+/87079413:48
kashyapChrist, it merged at last13:50
gibikashyap: it wasn't that long:)13:53
kashyapgibi: You're right though.  I tend to be a bit of a drama queen sometimes; please ignore me :)13:53
kashyapgibi: Thank you both for the help!  Now hope the API replacement patch goes through soon13:54
bauzassean-k-mooney: any docs you could point me out on the new direction for system roles ?13:54
kashyap(Thanks, sahid for rechecking it while I was away :))13:54
sean-k-mooneybauzas: gmann might have the links more redilaly but i think we updated the goal with it too13:56
sean-k-mooneybauzas: like this was a very very big thing that we have talked about before 13:56
sean-k-mooneyhttps://github.com/openstack/governance/commit/1909d4f7a0dc2920fc04ab5bfac112a671547cee13:56
bauzas" In yoga cycle, we redefined this goal with the changes mentioned above so that allowing system administrators to access system level resources APIs only and allow project users to access project-level resource APIs. These changes have been done for nova and neutron. "13:56
bauzassean-k-mooney: problem is, sometimes my brain splits13:57
sean-k-mooneyit was actully in zed13:57
bauzasso  it looks to me I probably heard about it, but then it wasn't ringing the bell in my brain when I saw today's change13:57
sean-k-mooneywell it depnes but that commit has the relevent info in it13:57
sahidkashyap: sure :-)14:01
*** dasm|off is now known as dasm14:03
sean-k-mooneykashyap: now all you have to do is backport it all the way to train and then cerry pick it downstream :P14:10
sean-k-mooneyso for 2 patchs that only 20 ish commits to create and review14:11
sean-k-mooneywith that said im not sure we need to backport the second patch14:11
sean-k-mooneythe frist we should but using the new api is less imporant14:12
opendevreviewAlexey Stupnikov proposed openstack/nova stable/zed: Remove deleted projects from flavor access list  https://review.opendev.org/c/openstack/nova/+/87005314:18
opendevreviewSahid Orentino Ferdjaoui proposed openstack/nova master: compute: enhance compute evacuate instance to support target state  https://review.opendev.org/c/openstack/nova/+/85838314:26
opendevreviewSahid Orentino Ferdjaoui proposed openstack/nova master: api: extend evacuate instance to support target state  https://review.opendev.org/c/openstack/nova/+/85838414:26
sahid^ fixed compute part, and owrking on the API one14:27
sahidfor the API part, is a BadRequest returned sounds good? in case that the rpc is not right and user is using new version?14:29
sahidor do you have in mind an other http status?14:30
sahidsean-k-mooney, bauzas ^ if you have a sec14:30
bauzassahid: we agreed yesterday on returning a HTTP409 Conflict14:31
sahidack14:31
bauzasI think we have existing exceptions that do those14:31
sean-k-mooneywe do14:46
sean-k-mooneywe use 409 conflict anythime we dont meet the required min compute service version and in a few other cases14:46
sean-k-mooneywe used to have a mix of code but we normalised on 409 about 3 cyles ago14:46
sean-k-mooneyit used to be diffent between pmem cyborg, numa/sriov migrations ectra14:47
kashyapsean-k-mooney: Heh, on the backports ... I need a bit of a breather for a few hours first from it14:49
sean-k-mooneyno worries but please propose them upstream before the downstream ones so we get the ci coverage14:49
kashyapAh, definitely14:50
kashyapHow far back we wanna go upstream?14:50
sean-k-mooneyso 16 is train if you want to go to 16 downstream then please do it upstream to trian too14:51
sean-k-mooneyif this is just for 17/wallaby you can stop there14:51
opendevreviewSahid Orentino Ferdjaoui proposed openstack/nova master: api: extend evacuate instance to support target state  https://review.opendev.org/c/openstack/nova/+/85838414:51
sean-k-mooneythis change shoudl be pretty safe to backprot and i dont really expect confligt14:52
kashyapYep14:52
sean-k-mooneyso hopefully its simple to do14:52
kashyapI only wonder about the small logical change of the switch to using _get_cpu_model_mapping()14:54
sean-k-mooneynot using that in my view was an existing bug that shoudl have been fixed anyway14:55
sean-k-mooneyso i think its ok14:55
sean-k-mooneywe can see what elodilles thinks14:55
sean-k-mooneyor other stable cores when the first review is up14:55
sahidsean-k-mooney, bauzas ok so i fixed the tests on compute and conductor, and changed the s/NovaException/... then i fixed REST API + tests with a HTTPConflict14:56
sean-k-mooneysahid++15:00
sean-k-mooneyi am just joinging a call but ill look when im free15:00
sahidsean-k-mooney: cool thanks you, but let me ping you when CI is green, no need that you lost your time if something fails that i have not noticed ;)15:01
sean-k-mooneysure im in calls for the hour or two15:03
opendevreviewAlexey Stupnikov proposed openstack/nova master: Add functional tests to reproduce bug #1994983  https://review.opendev.org/c/openstack/nova/+/86341615:20
opendevreviewAlexey Stupnikov proposed openstack/nova master: Log some InstanceNotFound exceptions from libvirt  https://review.opendev.org/c/openstack/nova/+/86366515:20
opendevreviewAlexey Stupnikov proposed openstack/nova stable/victoria: Add functional tests to reproduce bug #1960412  https://review.opendev.org/c/openstack/nova/+/84575315:38
opendevreviewAlexey Stupnikov proposed openstack/nova stable/victoria: Clean up when queued live migration aborted  https://review.opendev.org/c/openstack/nova/+/84575415:38
gmannbauzas: gibi: for tempest pin on wallaby, skiptest exception is due to incompatible version of stestr in constraints. I am checking it with what tempest version work on wallaby stestr constraint. 16:45
bauzasgmann: ack thanks16:46
gmannbauzas: for placement rbac system scope, in zed cycle direction of RBAC we have decided to drop the system scope from services that is why every policy is made to project scoped https://github.com/openstack/governance/commit/1909d4f7a0dc2920fc04ab5bfac112a671547cee16:46
gibigmann: thanks16:46
bauzasgmann: yup, my brain dumped this16:46
bauzassahid: you made a wrong assumption when writing the conductor unittest https://review.opendev.org/c/openstack/nova/+/858383/26/nova/tests/unit/conductor/test_conductor.py#4775 16:57
bauzasthe test should pass with the call be accepted without this parameter16:57
sahidbauzas: hum let me check17:00
sahidhum right we should not raise an exception here, I have done that too fast and for some reason when i have executed them locally i did not noticed..17:03
sahidbauzas: have you noticed something else that I can fix in that same time>17:03
sahid?17:03
opendevreviewSahid Orentino Ferdjaoui proposed openstack/nova master: compute: enhance compute evacuate instance to support target state  https://review.opendev.org/c/openstack/nova/+/85838317:11
opendevreviewSahid Orentino Ferdjaoui proposed openstack/nova master: api: extend evacuate instance to support target state  https://review.opendev.org/c/openstack/nova/+/85838417:11
dansmithsean-k-mooney: btw I think the stable compute series is ready for serious review and/or merging with two exceptions 1. some nits from gibi I will do as a FUP, and 2. working on trivial unit tests for the top rename patch17:30
dansmithbut it passes with the experimental ironic job and everything17:31
dansmithI guess maybe a test patch against ironic to run all their jobs might be prudent, let me get that in the pipe17:31
opendevreviewGhanshyam proposed openstack/placement master: Modify the placement API policies defaults and scope_type  https://review.opendev.org/c/openstack/placement/+/86561817:32
opendevreviewMerged openstack/nova master: libvirt: Replace usage of compareCPU() with compareHypervisorCPU()  https://review.opendev.org/c/openstack/nova/+/86995017:50
*** EugenMayer42 is now known as EugenMayer418:12
sean-k-mooneydansmith: i saw gibis review earlier ya and was wondering about the rest of the sereise18:27
sean-k-mooneygibis comment was about using a fixutre right 18:27
gibiyeah I had testing nits18:29
gibinothing serious18:29
sean-k-mooneydansmith: ok ill review the seriese tomorrow. im planning to deploy devstack tomorrow anyway so ill try the stable uuid series after i get that deployed and do a full pass on it18:30
dansmithsean-k-mooney: cool, sounds like a plan thanks18:30
dansmiththe ironic test job on top is about half done, all green so far18:30
* sean-k-mooney also has not deployed devstack since november...18:30
sean-k-mooneydansmith: oh you have a dnm patch for that already cool18:31
dansmithyeah I'll paste a link in the last patch when it's done if it looks good18:34
sean-k-mooneydansmith: one thing about the series. i dont see a release note and i dont think you have docs for this do you?18:37
dansmithsean-k-mooney: no and no18:37
dansmithsean-k-mooney: I'll get going on that, but let's not hold up on that, if possible :)18:37
sean-k-mooneyok so maybe another patch on the end for that or put it in the WIP patch18:38
sean-k-mooneyi think we can proceed before that i do trust you to write those just something that jumped out at me when i skimmed over the seriese18:38
dansmithI'll put the reno in the current last patch and then docs after yeah18:38
sean-k-mooneycool works for me18:38
dansmithI need to push up the unit tests I have, just waiting for ironic to finish, so reno can go in there and then I'll do the docs after18:39
sean-k-mooneyi dont think any of this code really does anything until "Persist existing node uuids locally" so we can proably merge the first three tomrrow gibi is already +2 on those18:40
sean-k-mooneyi need to go push something else but i might start on the first 3 this evening18:41
dansmithsure, that sounds good18:42
sean-k-mooneybut im only around for another 30 mins or so today then i need to go eat something18:42
dansmiththe persist one is also not super impactful, but it does do stuff18:42
dansmiththe resource tracker one is where the rubber meets the road for the first time18:42
*** EugenMayer46 is now known as EugenMayer419:04
opendevreviewDan Smith proposed openstack/nova master: Detect host renames and abort startup  https://review.opendev.org/c/openstack/nova/+/86392019:14
opendevreviewDan Smith proposed openstack/nova master: Detect host renames and abort startup  https://review.opendev.org/c/openstack/nova/+/86392019:47
opendevreviewDan Smith proposed openstack/nova master: Fixup patch for stable-compute-uuid series  https://review.opendev.org/c/openstack/nova/+/87184819:47
sean-k-mooney[m]dansmith:  i did a first pass i have one or two question later in the series the first 3 should be in the gate21:50
dansmithsean-k-mooney: ack, thanks, I saw the first three, I'll look at the others in a bit or tomorrow21:51
gmanngibi: updated the placement RBAC change https://review.opendev.org/c/openstack/placement/+/86561822:30
opendevreviewMerged openstack/nova master: Add virt/node module for stable uuids  https://review.opendev.org/c/openstack/nova/+/86391522:48
opendevreviewMerged openstack/nova master: Pass service ref to init_host(), if exists  https://review.opendev.org/c/openstack/nova/+/86391622:48
*** dasm is now known as dasm|off23:13

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