Wednesday, 2019-04-10

*** tjgresha has quit IRC00:00
*** betherly has quit IRC00:04
*** tetsuro has joined #openstack-nova00:14
*** tbachman has quit IRC00:23
*** dakshina-ilangov has quit IRC00:24
*** lbragstad has quit IRC00:45
openstackgerritMerged openstack/nova stable/rocky: Replace openstack.org git:// URLs with https://  https://review.openstack.org/64668600:46
*** tbachman has joined #openstack-nova00:51
*** tetsuro has quit IRC00:58
*** Cardoe has quit IRC01:01
*** medberry has joined #openstack-nova01:01
*** Cardoe has joined #openstack-nova01:02
*** gyee has quit IRC01:03
*** medberry has quit IRC01:05
*** betherly has joined #openstack-nova01:11
*** whoami-rajat has joined #openstack-nova01:12
*** tiendc has joined #openstack-nova01:13
*** betherly has quit IRC01:16
*** mriedem has quit IRC01:18
*** openstackgerrit has quit IRC01:30
*** nicolasbock has quit IRC01:45
*** openstackgerrit has joined #openstack-nova01:51
openstackgerritmelanie witt proposed openstack/nova master: Use futurist.GreenThreadPoolExecutor in scatter_gather_cells  https://review.openstack.org/65017201:51
*** betherly has joined #openstack-nova01:53
*** betherly has quit IRC01:57
*** hongbin has joined #openstack-nova02:29
*** owalsh_ has joined #openstack-nova02:34
*** owalsh has quit IRC02:34
*** cfriesen has quit IRC02:37
openstackgerritBoxiang Zhu proposed openstack/nova master: Use the functional test test_parallel_evacuate_with_server_group  https://review.openstack.org/64996302:44
*** betherly has joined #openstack-nova02:45
openstackgerritLi Zhouzhou proposed openstack/nova stable/queens: SRIOV pci_numa_policy dosen't working when create instance with 'cpu_policy' and 'numa_nodes  https://review.openstack.org/65142902:45
*** betherly has quit IRC02:50
*** psachin has joined #openstack-nova03:01
*** mmethot has quit IRC03:09
*** mmethot has joined #openstack-nova03:09
*** udesale has joined #openstack-nova03:26
*** ricolin has joined #openstack-nova03:31
*** hongbin has quit IRC03:42
*** imacdonn_ has quit IRC04:03
*** imacdonn_ has joined #openstack-nova04:03
*** sridharg has joined #openstack-nova04:04
*** dave-mccowan has quit IRC04:15
*** betherly has joined #openstack-nova04:18
*** betherly has quit IRC04:23
*** openstackstatus has quit IRC04:35
*** openstackstatus has joined #openstack-nova04:36
*** ChanServ sets mode: +v openstackstatus04:36
*** tetsuro has joined #openstack-nova04:59
*** betherly has joined #openstack-nova05:00
*** ratailor has joined #openstack-nova05:01
*** betherly has quit IRC05:04
*** pcaruana has joined #openstack-nova05:06
*** Luzi has joined #openstack-nova05:17
*** ricolin has quit IRC05:30
*** sidx64 has joined #openstack-nova05:42
*** shilpasd has joined #openstack-nova05:45
*** gerrykopec_ has quit IRC05:53
kaisersefried: Thanks for looking. I'm busy with other stuff atm but will follow up on your feedback later on!06:15
*** janki has joined #openstack-nova06:19
*** bhagyashris_ has joined #openstack-nova06:33
*** ralonsoh has joined #openstack-nova06:36
*** luksky has joined #openstack-nova06:45
*** liuyulong_ has joined #openstack-nova06:50
*** slaweq has joined #openstack-nova07:00
*** rpittau|afk is now known as rpittau07:05
*** awalende has joined #openstack-nova07:08
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove deprecated 'default_flavor' config option  https://review.openstack.org/64547607:09
*** tesseract has joined #openstack-nova07:09
*** tesseract has quit IRC07:10
*** tesseract has joined #openstack-nova07:10
*** ivve has joined #openstack-nova07:12
*** owalsh_ is now known as owalsh07:17
* alex_xu very enjoy on reply the comment from sean-k-mooney07:24
*** tssurya has joined #openstack-nova07:26
*** tosky has joined #openstack-nova07:28
*** psachin has quit IRC07:32
*** pcaruana has quit IRC07:34
*** pcaruana has joined #openstack-nova07:35
*** psachin has joined #openstack-nova07:35
*** lpetrut has joined #openstack-nova07:41
*** boxiang has quit IRC07:45
*** ccamacho has joined #openstack-nova07:45
*** boxiang has joined #openstack-nova07:46
openstackgerritAdrian Chiris proposed openstack/nova master: libvirt: auto detach/attach sriov ports on migration  https://review.openstack.org/62958907:47
sean-k-mooneyalex_xu: which comment wast that?08:00
sean-k-mooneyi didnt get time to review as much specs yesterday as i would have liked but i assume one of the cpu frequencey specs?08:00
sean-k-mooneyalex_xu: ah i see you replied on https://review.openstack.org/#/c/649882/ ill take another look in an hour or so08:02
*** tkajinam has quit IRC08:04
*** priteau has joined #openstack-nova08:05
*** phasespace has quit IRC08:08
openstackgerritBoxiang Zhu proposed openstack/nova-specs master: Add host and hypervisor_hostname flag to create server  https://review.openstack.org/64545808:09
*** luksky has quit IRC08:11
*** evrardjp has quit IRC08:18
*** evrardjp has joined #openstack-nova08:19
*** Luzi has quit IRC08:21
*** ttsiouts has joined #openstack-nova08:27
openstackgerritBoxiang Zhu proposed openstack/nova-specs master: Add host and hypervisor_hostname flag to create server  https://review.openstack.org/64545808:27
*** ricolin has joined #openstack-nova08:30
*** derekh has joined #openstack-nova08:35
openstackgerritBoxiang Zhu proposed openstack/nova-specs master: Add host and hypervisor_hostname flag to create server  https://review.openstack.org/64545808:44
*** luksky has joined #openstack-nova08:50
*** liuyulong_ has quit IRC08:50
alex_xusean-k-mooney: thanks!08:58
*** dtantsur|afk is now known as dtantsur08:58
alex_xusean-k-mooney: I mean all of them, they are good comments :)08:58
alex_xusean-k-mooney: I saw you like the extra spec defined in https://review.openstack.org/#/c/651024/5/specs/train/approved/rmd-plugin-energy-efficiency-core-p-states-control.rst@310, but I'm not quite understand, it will be great you have an example for it, if it is good, I'm happy to change also09:02
alex_xufor now, I need to offline for catching my daughter09:02
sean-k-mooneyok o/09:02
alex_xuthanks!09:02
sean-k-mooneyand ya i like it more as its a finite set09:03
sean-k-mooneyusing arbiarty traits makes me a little uneasy09:03
alex_xuah, i see now09:03
sean-k-mooneyit could be fine just need to get used to the idea09:03
alex_xubut I don't want to assume there are only two priority(high and low), the user may have their own configuration, they can have some custom tratis09:04
alex_xuanyway, I have to go, catch up you later09:04
sean-k-mooneythey may but that is an interoperablity headache between clouds. sure dont be late for dad taxi service :)09:05
*** ttsiouts has quit IRC09:18
*** ttsiouts has joined #openstack-nova09:19
*** ttsiouts has quit IRC09:23
*** tetsuro has quit IRC09:24
*** phasespace has joined #openstack-nova09:30
*** ociuhandu has quit IRC09:35
*** rchurch has quit IRC09:44
*** rchurch has joined #openstack-nova09:45
kashyapalex_xu: sfinucan: After some more thinking last night, I'm updating that `cpu_model_list` spec a bit more09:46
kashyapErr, stephenfin ^ :-)09:47
kashyapstephenfin: On the name, I'm responding on the change...but quickly here: I didn't even think of the "Hungarian Notation" until you mentioned :-009:47
kashyapBut I see your point, though.09:47
*** rcernin has quit IRC09:47
kashyapIMHO, it's just unambiguously clear to go with the _list; instead of playing with alises and such.09:48
stephenfinkashyap: Yeah, I really don't think it's necessary. oslo.config is powerful enough to let us handle the migration issues, as I noted09:48
kashyapI've seen far too many such subtle and confusing mistakes in config attributes in the past.  :-(09:48
stephenfinPerhaps, but you're going to have to use aliases anyway, assuming you want to remove the current value at some point in the future09:48
sean-k-mooneykashyap: useing _list may be clear but it breaks convention09:49
kashyapI see.  It's not merely the technical.  But I'm still not convinced from the human / operator "visual clarity"09:49
kashyapsean-k-mooney: What convention?  We should break "conventions" when it makes sense.09:49
stephenfinI think that matters less than you think. People don't set nova.conf files, tools do09:49
sean-k-mooneythe conventions of we just use the plural form to denote lists in the config09:49
stephenfinBe that TripleO, Kolla, or something else09:49
kashyapYeah, realize it as much.  I want to wait a bit more to convince myself09:50
sean-k-mooneykashyap: im not arguing _list is wronge im just saying i dont think its that important if its _list or plural09:50
kashyap(I'm not convinced.  I'll think a bit more and write on the review.)  But there's more important bits in that spec to tackle, though09:51
stephenfinsean-k-mooney: If I resize an instance, does that instance move host?09:51
kashyap(The more I think about this topic, the more subtle questions I can think of...)09:51
stephenfins/does/can/09:51
sean-k-mooneynot in all cases but it is allowed too move09:51
sean-k-mooneyrebuilds are always to the same host but resize default to migration but you can enable resize to same host in the config in which case we dont add the current host to the ingroed host list09:52
*** boxiang has quit IRC09:52
*** boxiang has joined #openstack-nova09:53
*** bhagyashris_ has quit IRC09:54
*** ttsiouts has joined #openstack-nova09:57
sean-k-mooneystephenfin: does that make sesnse ^09:58
stephenfinsean-k-mooney: It sure does09:58
*** ttsiouts has quit IRC10:07
*** tiendc has quit IRC10:08
*** tbachman has quit IRC10:13
*** tssurya has quit IRC10:31
*** cdent has joined #openstack-nova10:33
*** brinzhang has joined #openstack-nova10:48
*** erlon has joined #openstack-nova10:48
*** tbachman has joined #openstack-nova10:50
*** nicolasbock has joined #openstack-nova10:52
yaawangbauzas: stephenfin Thanks for your review. I agree with your comments about not expose driver's feature to the REST api. So how about putting these into the flavor extra flags and image metadata? Use these properties to datermine whether to use 'auto converge' or 'post copy' during live migration.11:00
*** jamesdenton has quit IRC11:03
*** nowster has joined #openstack-nova11:06
*** ttsiouts has joined #openstack-nova11:06
*** tssurya has joined #openstack-nova11:08
*** brinzhang has quit IRC11:11
*** erlon has quit IRC11:16
*** jamesdenton has joined #openstack-nova11:20
tridentAre there any specific reasons why block migration is not implemented with the LVM backend? Any specific issues with getting it to work or just that nobody has implemented support for it?11:22
*** udesale has quit IRC11:24
*** udesale has joined #openstack-nova11:24
*** cdent_ has joined #openstack-nova11:29
*** cdent has quit IRC11:31
*** cdent_ is now known as cdent11:31
*** aloga has quit IRC11:35
*** aloga has joined #openstack-nova11:36
*** sidx64 has quit IRC11:39
kashyapstephenfin: Idea: Is this any palatable: `acceptable_cpu_models`?  (It closely captures the intended meaning _and_ we can avoid "Hungarian")11:47
*** dpawlik has joined #openstack-nova11:47
kashyap(I am wary of bike-shedding, while knowing that "naming is hard", so want to avoid mistakes when I can. :-))11:47
kashyap(Context to others: By "Hungarian", /me was referring to the "Hungarian Notation" -- https://en.wikipedia.org/wiki/Hungarian_notation)11:48
*** sidx64 has joined #openstack-nova11:50
*** rabel has joined #openstack-nova11:57
rabelhi there. if a hypervisor has a negative disk_available_least value, but free space on the disk (local storage, qcow2 images). and now it does not allow live migrations to this hypervisor. is it sufficient to increase disk_allocation_ratio to make this hv available for live migration again?11:58
kashyapMaybe `acceptable_cpu_models` is not acceptable; it breaks the "symmetry" of existing config, options which all start with: cpu_{mode, model|models|model_list, extra_flags}11:59
*** udesale has quit IRC11:59
*** maciejjozefczyk has joined #openstack-nova11:59
*** eharney has joined #openstack-nova12:06
*** tbachman has quit IRC12:06
*** chhagarw has joined #openstack-nova12:06
*** sidx64 has quit IRC12:06
*** ttsiouts has quit IRC12:08
*** ttsiouts has joined #openstack-nova12:09
*** sidx64 has joined #openstack-nova12:09
*** priteau has quit IRC12:12
*** ttsiouts has quit IRC12:13
*** tbachman has joined #openstack-nova12:13
*** priteau has joined #openstack-nova12:14
sean-k-mooneykashyap: enabled_cpu_models would be similar to enabled_filters for the schduler12:16
*** dave-mccowan has joined #openstack-nova12:17
sean-k-mooneybut also i think both are verbose and we can use something shorter12:17
kashyapA little verbose is OK, so long as it conveys intended meaning.  I'll stick to `cpu_model_list` for now.  It is just unambiguous.12:18
*** sidx64 has quit IRC12:19
*** avolkov has joined #openstack-nova12:21
sean-k-mooneykashyap: its also a chose that several people dislike but as i said it dotn care enough to rathole on it12:22
*** awalende has quit IRC12:26
*** awalende has joined #openstack-nova12:26
*** sidx64 has joined #openstack-nova12:31
*** awalende has quit IRC12:31
rabelnvm my question. it seems we were hitting https://bugs.launchpad.net/nova/+bug/170857212:36
openstackLaunchpad bug 1708572 in OpenStack Compute (nova) "Unable to live-migrate : Disk of instance is too large" [High,Fix released] - Assigned to Matthew Booth (mbooth-9)12:36
*** udesale has joined #openstack-nova12:36
*** tbachman has quit IRC12:37
*** sidx64 has quit IRC12:38
*** tbachman has joined #openstack-nova12:42
*** awaugama has joined #openstack-nova12:45
alex_xukashyap: in the initial spec discussion, we said we can't done the check without hypervisour-literate api https://review.openstack.org/#/c/620959/5..9/specs/stein/approved/cpu-model-selection.rst@6312:50
alex_xulet me what we changed now :)12:50
*** ricolin has quit IRC12:50
* kashyap clicks and re-reads12:50
*** ttsiouts has joined #openstack-nova12:51
*** ricolin has joined #openstack-nova12:51
*** lbragstad has joined #openstack-nova12:58
*** udesale has quit IRC13:01
*** lpetrut has quit IRC13:01
*** mriedem has joined #openstack-nova13:02
*** udesale has joined #openstack-nova13:03
*** irclogbot_0 has joined #openstack-nova13:03
kashyapalex_xu: Being dragged into a meeting; will respond there13:05
*** sidx64 has joined #openstack-nova13:06
*** altlogbot_1 has joined #openstack-nova13:07
*** sidx64 has quit IRC13:08
*** sidx64 has joined #openstack-nova13:09
*** sidx64 has quit IRC13:10
alex_xukashyap: no hurry13:11
*** dklyle has joined #openstack-nova13:17
*** maciejjozefczyk has quit IRC13:19
*** mvkr has quit IRC13:19
*** maciejjozefczyk has joined #openstack-nova13:21
*** maciejjozefczyk has quit IRC13:21
sean-k-mooneystephenfin: i think https://review.openstack.org/#/c/648123/4 looks good now13:28
sean-k-mooneyalex_xu: efried care to take a look ^ i think this is a fairly simple fix13:28
efriedsean-k-mooney: Wow, that has more words in the title that I don't understand than that I do.13:30
efriedsean-k-mooney: If you get desperate I'll take a look, but you should find someone more familiar with the subject matter.13:30
sean-k-mooneyefried: no worries13:31
alex_xusean-k-mooney: I can do tomorrow, I don't think I have clear mind now13:31
sean-k-mooneyalex_xu: specs have that effect13:31
alex_xuhah :)13:32
*** sidx64 has joined #openstack-nova13:34
*** phasespace has quit IRC13:36
alex_xuthat is really bad to see jaypipes's strong -1 just after decide end the day :)13:38
*** sidx64 has quit IRC13:39
alex_xuanyway, I will leave it to tomorrow13:40
*** ratailor has quit IRC13:43
*** tbachman has quit IRC13:47
*** tbachman has joined #openstack-nova13:47
artomsean-k-mooney, you OK with the tests refactor being in the same patch as the actual fix?13:51
artomI'm kinda leaning towards splitting that in two patches?13:51
*** mvkr has joined #openstack-nova13:53
sean-k-mooneyartom: are you refering to https://review.openstack.org/#/c/648123/413:57
artomsean-k-mooney, yeah. Just left a revirw13:58
artom*review13:58
sean-k-mooneyartom: i did ask myself that question and the anser was "meh" ill see if anyone else cares13:58
*** mlavalle has joined #openstack-nova13:58
sean-k-mooneyfor backporting would likely be simpler to have them as seperate patches i gues13:58
sean-k-mooneybecause the test refactor was related to the change i was ok with it but normally i would have prefered them to be split13:59
artomsean-k-mooney, well I have a -1 for other small nits, we'll let others make that call for us :D14:01
artomSince we both appear to be "meh" :)14:01
*** mchlumsky has joined #openstack-nova14:01
sean-k-mooneyartom: on the api question there are times where this works today and it ends up in the api with the mac but not stats14:02
sean-k-mooneyartom: so i dont think its an api change14:03
artomsean-k-mooney, that's what I had understood as well14:03
artomAnd the test does assert one of the fields is None, so we're probably covered14:03
*** amodi has joined #openstack-nova14:04
sean-k-mooneyoh i didnt put https://bugzilla.redhat.com/show_bug.cgi?id=1649688#c8 into the upstream bug14:04
openstackbugzilla.redhat.com bug 1649688 in openstack-nova "[osp13] nova diagnostics command is not working with all instances" [High,Assigned] - Assigned to fpalin14:04
sean-k-mooneyactully there might be a slight api change in that before nic_details was empty and no i has a mac14:05
*** phasespace has joined #openstack-nova14:05
sean-k-mooneybut i dont think that is versioned but good question14:06
artomI don't think it'd have been empty before, rather an error 5014:07
artom50014:07
sean-k-mooneyno it was empty when i tried to reporduce the bug on my local systlem14:08
sean-k-mooneyif the vf has a netdev before its plug libvirt added the target element and we did not raise an error but you had no data at all14:08
artomHrmm, in any case, None is still allowed in fields14:09
artomSo nic_details = None is valid, as is nic_detail = {mac: blah, rest of fields: None}14:09
sean-k-mooneywell we dont have any tests assering the api behavior so i think there is some flexibity here. we can either say its fine as it is and this was a bug that was fixed and there does not need a microverion or there is no testing therfor it was broke by default and this fixed it :)14:13
*** janki has quit IRC14:13
artomWell we have an api-ref and a when-to-microversion flow chart14:13
sean-k-mooneybut i dont think its being to checky to say it does not need a microverions14:13
artomAnd fixing 500 errors is NOT a new microversion14:14
sean-k-mooneywe do14:14
sean-k-mooneycorrect14:14
artomI was just concerned the fields would be *missing* outright14:14
*** openstackgerrit has quit IRC14:14
artomWhich is moot, because it doesn't appear to be the case, but would have required a new microversion, or more likely an updated patch that didn't have that problem14:14
sean-k-mooneyyep well this is why we have code review is a valid concern i think we are ok however.14:15
* sean-k-mooney runs for lunch brb14:16
*** slaweq has quit IRC14:16
mriedemboxiang: just a few small things to address in your spec here https://review.openstack.org/#/c/645458/14:24
mriedembut i know it's late so feel free to address those comments tomorrow14:24
*** openstackgerrit has joined #openstack-nova14:26
openstackgerritStephen Finucane proposed openstack/nova master: Bump to hacking 1.1.0  https://review.openstack.org/65155314:26
openstackgerritStephen Finucane proposed openstack/nova master: hacking: Resolve E731 issues  https://review.openstack.org/65155414:26
openstackgerritStephen Finucane proposed openstack/nova master: hacking: Resolve W503 issues  https://review.openstack.org/65155514:26
*** awalende has joined #openstack-nova14:27
gibimriedem: hi! when you implemented heal allocation in nova-manage did you thought about adding some kind of end-to-end test for it? I'm wondering how complex it would be to add something to grenade for the heal port allocation but I don't have enough grenade knowledge to see if it is feasible at all14:31
*** awalende has quit IRC14:31
openstackgerritBoxiang Zhu proposed openstack/nova master: Make evacuation respects anti-affinity rule  https://review.openstack.org/64996314:33
mriedemwhen i implemented it (in rocky? queens?) we were only healing basic resource class allocations like VCPU/MEMORY_MB/DISK_GB and only if they didn't exist, which by that time wouldn't be a problem if using the FilterScheduler - the command was really built to get people off the CachingScheduler which didn't use placement, and we didn't have a grenade job that used the CachingScheduler, so no i didn't really put much thought in14:33
mriedemntegration testing for that command14:33
gibimriedem: ack, thanks14:34
mriedemwe could have a post-test hook script run it from the nova-next job, but we'd have to fake the missing allocations by creating a server then manually removing it's allocations and then running the command and verify they were healed14:35
mriedemwhich...we can just do that in functional in-tree tests14:35
gibimriedem: yeah, I'm doing that in the func test already14:35
mriedembw provider ports is a whole other ball of wax - can we even test those in the gate?14:35
mriedemi mean we can test that you can create a min bw policy on a network and create ports on that network and make sure the allocations and such are all wired up14:36
mriedembut i'm not sure we can test that the bw is actually limited within the guest in the gate14:36
mriedemjust making sure nova+neutron+placement are all doing what they are supposed to (from the gate) would be a good step anyway14:36
gibimriedem: yeah I think we have such tempest test on review14:37
gibilet me look up the link14:37
*** cfriesen has joined #openstack-nova14:37
gibimriedem: https://review.openstack.org/#/c/629253/14:37
gibifor the heal port allocation we would need to create a bound port in rocky that would need allocation in stein14:38
gibiunfortunately in rocky only sriov ports supported min bw in neutron, and sriov is no no in the gate14:38
gibiI can trick the system by adding the min bw policy to the port _after_ it was bound but that feels hackis already14:39
mriedemagree14:39
gibiI think I wil stick to the functional test env for heal port allocation14:39
gibiand I might do some manual test in a devstack where I have sriov14:40
*** sridharg has quit IRC14:42
*** ttsiouts has quit IRC14:44
*** ttsiouts has joined #openstack-nova14:45
mriedemmelwitt: are you ok to re-approve the cross-cell resize spec https://review.openstack.org/#/c/642807/ ? I saw you were just +1. I'd like to get the blueprint re-approved so i can start putting the bottom tail of the (huge) series into runways to get some reviews going.14:46
*** ttsiouts has quit IRC14:47
*** ttsiouts has joined #openstack-nova14:47
*** artom has quit IRC14:50
*** sidx64 has joined #openstack-nova14:50
*** luksky has quit IRC14:51
stephenfinmriedem: Fancy revisiting this? https://review.openstack.org/#/c/650018/14:53
*** slaweq has joined #openstack-nova14:54
mriedem"I've spoken with Lars Kurth (XenProject advisory board chair) and he  agrees that at this point in time, this config can be removed."14:55
mriedemso we have no CI for libvirt+xen14:55
mriedemand no plans to14:55
mriedemok14:55
*** sidx64 has quit IRC14:57
*** sidx64_ has joined #openstack-nova14:57
mriedemstephenfin: back at you https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bug/182378114:57
stephenfinack14:58
stephenfinmriedem: Out of curiosity, does this look familiar to you? http://paste.openstack.org/show/P6AlRRpBWnYwFfWWVJFl/ It's a stable/rocky deployment14:59
mriedemyes i think so, sec15:00
mriedemactually no nvm, was thinking of something else pci related15:01
mriedemit's blowing up on this? "n_id = compute_node.id"15:02
mriedemi only see _setup_pci_tracker called with an existing compute node record where id should be set15:02
mriedemunless you guys have a fork15:02
stephenfinNot that I'm aware of. I had been doing some work in that area but none of that is merged yet :/ https://review.openstack.org/#/c/649559/15:04
stephenfinBut yeah, looks like that. I don't know if that attribute should be set or not. I can't see why it wouldn't but all things Ironic really aren't my strong suit15:05
melwittmriedem: I was thinking dansmith would want to sign off on it15:06
* stephenfin is currently tracing paths that create/modify ComputeNode objects to see where this might be missed15:06
*** tbachman has quit IRC15:08
mriedemstephenfin: i don't think that error has anything to do with ironic15:08
stephenfinPerhaps, but it's only happening with baremetal nodes so I suspect it's some with how we're initializing the Ironic driver15:13
stephenfinbut that's a grasp15:13
*** maciejjozefczyk has joined #openstack-nova15:14
mriedemso the driver returns a list of nodenames for that host and those get passed one at a time to RT https://github.com/openstack/nova/blob/stable/rocky/nova/compute/manager.py#L789315:15
*** jangutter_ is now known as jangutter15:15
mriedemshould eventually call through to here https://github.com/openstack/nova/blob/stable/rocky/nova/compute/resource_tracker.py#L74315:16
mriedemif the compute node already exists in the db you'd get here on first startup https://github.com/openstack/nova/blob/stable/rocky/nova/compute/resource_tracker.py#L56715:17
mriedemthis should also be ok https://github.com/openstack/nova/blob/stable/rocky/nova/compute/resource_tracker.py#L53015:18
*** tbachman has joined #openstack-nova15:18
mriedemotherwise we'd create the node in the db https://github.com/openstack/nova/blob/stable/rocky/nova/compute/resource_tracker.py#L58415:18
mriedemwhich should set the id on the cn object15:18
mriedemhttps://github.com/openstack/nova/blob/stable/rocky/nova/objects/compute_node.py#L32215:19
mriedemlooks like you've got some debugging to do if you can recreate it15:19
*** dave-mccowan has quit IRC15:23
*** dave-mccowan has joined #openstack-nova15:24
*** munimeha1 has joined #openstack-nova15:25
*** gyee has joined #openstack-nova15:26
*** ivve has quit IRC15:28
*** ccamacho has quit IRC15:28
*** efried has quit IRC15:28
*** artom has joined #openstack-nova15:29
*** _alastor_ has joined #openstack-nova15:29
*** _alastor_ has quit IRC15:30
*** _alastor_ has joined #openstack-nova15:30
mriedemlyarwood: melwitt: dansmith: bauzas: looks like we can start approving stable/stein backports now so i'll start going through those and removing the WIP on mine15:32
mriedemwe need to roll through some of those to get things flushed out down through pike for pike-em15:32
dansmith ack15:32
melwittah, yep15:32
melwittI have a bug fix that needs to go back to pike but it hasn't even merged on master yet and having trouble getting review https://review.openstack.org/61197415:33
cdentmriedem: does a server always get buried to cell0 when it fails to find a host? Is it possible to say "only bury if you requested a build at a microversion that will allow an unbury"?15:34
mriedemmelwitt: i definitely don't know that code so would need at least lyarwood and/or mdbooth to sign off15:34
mriedemcdent: "does a server always get buried to cell0 when it fails to find a host?" yes15:34
*** gerrykopec has joined #openstack-nova15:34
mriedem"Is it possible to say "only bury if you requested a build at a microversion that will allow an unbury"?" i think that gets really complicated fast15:35
cdenti imagine so15:35
cdentwhat was the original purpose of burying?15:35
dansmithyeah that's not okay15:35
mriedembecause it's more like (1) only bury if using a microversion to allow unburying except (2) unless you didn't request personality files etc15:35
melwittthere's this one too but people were meh about reviewing it too https://review.openstack.org/58240815:35
mriedemcdent: need to be able to show the servers from the API even though they are in error state and not on a host,15:36
dansmithcdent: it's still the original purpose, which is that if we didn't pick a host, we didn't pick a cell, thus we have nowhere to store it15:36
mriedemand the api pulls servers from a cell db15:36
mriedemwe have build_requests but those are short-lived15:36
cdentah, right, I keep forgetting that a server that is an ERROR is still a server (which is a decision I've never quite understood)15:36
mriedemmelwitt: it's failing pep8 :)15:37
bauzasmriedem: ack, sorry on a meeting15:37
*** tbachman has quit IRC15:38
melwittsigh15:38
openstackgerritSurya Seetharaman proposed openstack/nova master: Block automatic transport_url update for cell0  https://review.openstack.org/60541415:40
openstackgerritMerged openstack/nova-specs master: Re-propose cross-cell-resize spec for Train  https://review.openstack.org/64280715:46
*** efried has joined #openstack-nova15:47
*** sidx64_ has quit IRC15:51
*** artom has quit IRC15:51
*** rpittau is now known as rpittau|afk15:53
*** artom has joined #openstack-nova15:59
*** tesseract has quit IRC16:03
*** francoisp_ has joined #openstack-nova16:03
*** tbachman has joined #openstack-nova16:04
*** ociuhandu has joined #openstack-nova16:08
*** ociuhandu has quit IRC16:10
*** psachin has quit IRC16:14
*** efried is now known as efried_rollin16:14
*** dtantsur is now known as dtantsur|afk16:15
bauzasmelwitt: thanks for reviewing https://review.openstack.org/#/c/650963/ I replied to your question16:22
melwittbauzas: a-ha, thanks16:23
*** derekh has quit IRC16:28
melwittlyarwood, mdbooth: begging for reviews on this again, disk unit stuff https://review.openstack.org/61197416:30
*** ivve has joined #openstack-nova16:30
lyarwoodmelwitt: ack saw above, I'll take a look once I've finished with all of this downstream paperwork... bugzilla--16:30
melwittoh cool, sorry for the double ping16:30
lyarwoodnp at all16:31
mriedemefried_rollin: want to drop the -W on https://review.openstack.org/#/c/649600/ ?16:34
openstackgerritTheodoros Tsioutsias proposed openstack/nova-specs master: Enable rebuild for instances in cell0  https://review.openstack.org/64868616:35
openstackgerritmelanie witt proposed openstack/nova master: Add functional recreate test for bug 1764556  https://review.openstack.org/56204116:37
openstackbug 1764556 in OpenStack Compute (nova) ""nova list" fails with exception.ServiceNotFound if service is deleted and has no UUID" [Medium,In progress] https://launchpad.net/bugs/1764556 - Assigned to melanie witt (melwitt)16:37
openstackgerritmelanie witt proposed openstack/nova master: Add functional regression test for bug 1778305  https://review.openstack.org/58240716:37
openstackgerritmelanie witt proposed openstack/nova master: Don't generate service UUID for deleted services  https://review.openstack.org/58240816:37
openstackbug 1778305 in OpenStack Compute (nova) "Nova may erronously look up service version of a deleted service, when hostname have been reused" [Undecided,In progress] https://launchpad.net/bugs/1778305 - Assigned to melanie witt (melwitt)16:37
*** ttsiouts has quit IRC16:40
*** ttsiouts has joined #openstack-nova16:41
*** ttsiouts has quit IRC16:45
mriedemmlavalle: did you sort out the NoValidHost error you were getting the other night?16:46
mlavallemriedem: yes, thanks for following up. it was the image filter16:46
*** altlogbot_1 has quit IRC16:46
*** phasespace has quit IRC16:47
mriedemmlavalle: ok so you have some image with metadata that didn't match any hosts i'm guessing?16:47
dansmithmriedem: were you going to un-WIP your stein backports?16:47
mriedemdansmith: just finished16:47
mlavallemriedem: excatly and sisnce I have only one compute, that was the end of that request16:48
dansmithokay gerrit didn't notify me16:48
mriedemmlavalle: did enabling debug in the scheduler and checking the logs tell you what was up? or did you have to then look at the code too?16:48
stephenfinmriedem: fwiw, your assumption that the issue I pointed out earlier wasn't ironic specific seems to have proven out. I spotted this after http://paste.openstack.org/show/fsWdgjpwsycPzdqPXNLI/16:49
stephenfinNot sure why that's happening (I suspect something HA'y) but that would explain why ID, an auto-incremented primary key field (I assume) wasn't set16:49
stephenfinI found a similar issue reported by MarkusZ years ago that I need to look into more, but that's tomorrow's work https://bugs.launchpad.net/nova/+bug/1566783/comments/416:50
openstackLaunchpad bug 1566783 in OpenStack Compute (nova) "On service start, nova-compute fails to register itself to the DB" [Low,Confirmed]16:50
mriedemstephenfin: that's a failure to create the compute node in the db because some other node with the same uuid already exists, but you wouldn't have a compute_nodes table record without an id16:50
stephenfinJust closing that loop :)16:50
mriedemso i still don't understand how you'd get that object action error on loading ComputeNode.id16:50
*** ivve has quit IRC16:51
mlavallemriedem: without enabling debug, the conductor log gave the filter that was failing. at the end the conductor logs how many hosts each filter returns. All the filters looked something like: in: 1, out 1. The image filter was: in: 1, out: 016:51
* mlavalle is paraphrasing. I don't remember the eaxcat notation16:51
stephenfinmriedem: I figured the initial object creation was failing so we're left with a Python object but no underlying DB entry16:51
mriedemmlavalle: sure, just wondering if it was really hard to figure out but sounds like it wasn't16:51
mriedemstephenfin: we shouldn't even get to _setup_pci_tracker in that case though16:52
mlavallemriedem: nop, just looking closer at the logs. I guess when I pinged you, it was Friday, night and I was tired..... Or maybe I just needed an excuse to say hi ;-)16:52
mriedemstephenfin: i.e. if this fails https://github.com/openstack/nova/blob/stable/rocky/nova/compute/resource_tracker.py#L584 you're not going to be calling https://github.com/openstack/nova/blob/stable/rocky/nova/compute/resource_tracker.py#L58916:53
mriedemthe question would be why would we even try to create the compute node record if it already exists by uuid16:53
*** wolverineav has joined #openstack-nova16:53
mriedembecause https://github.com/openstack/nova/blob/stable/rocky/nova/compute/resource_tracker.py#L567 should find the existing cn in the db16:53
mriedemunless,16:54
mriedemthe hypervisor_hostname is different16:54
stephenfinCould it be racy if you've multiple compute services running?16:54
sean-k-mooney i was going to say we lookup the compute service by hostname to get the uuid16:54
mriedemit could race if you've got multiple compute services trying to manage the same node yeah16:55
*** wolverineav has quit IRC16:56
sean-k-mooneyor multiple nodes with the same hostname?16:56
mriedemstephenfin: do you have this fix? https://github.com/openstack/nova/commit/57566f4c8d2929c25e76564883369a7c6eda720a16:56
*** wolverineav has joined #openstack-nova16:56
* stephenfin checks16:57
mriedemsean-k-mooney: i'm not sure what you're saying16:57
mriedem"compute service by hostname to get the uuid" is wrong though in this case16:57
mriedemcompute nodes in the db are 1:1 with ironic nodes, and in this case we're looking up the compute node by nodename, i.e. hypervisor_hostname, i.e. ironic node.uuid16:57
mriedemnot the nova-compute service hostname16:57
sean-k-mooneyoh this is ironic never mind16:57
stephenfinDamn it, I've to go (tag rugby match in 15 minutes). Sorry /o\16:58
mriedemback to the pile16:58
stephenfinyuuuup16:58
* mriedem gets lunch16:59
sean-k-mooneyi was going to say if there are two hosts with the same hostname in the cloud then the both endup sharing the same compute service and hypervior entry in the db and evertying is broken.16:59
sean-k-mooneythats not related to that however16:59
cfriesenoff-the-wall question here...with the rise of containerized openstack services it's a bit of a pain to tweak the code since killing the running service kills the container.  has anyone considered a way to "hot reload" new code without killing the running nova process?17:00
sean-k-mooneycfriesen: as in via a SIG_HUP17:00
sean-k-mooneyi dont think so17:01
sean-k-mooneywhats the issue with restarting the container17:01
cfriesensean-k-mooney: you have to make a new image, then tag it, and upload it to the repository, then tell helm to use the new image...17:01
cdentor starting a different container to take over17:02
sean-k-mooneycdent: oh i taught you meet jsut execing into the contanter and patching it17:02
sean-k-mooneycfriesen: ^17:02
cfriesensean-k-mooney: that's what I'd like to do17:02
cfriesensean-k-mooney: but if you stop nova-compute (for example) the container dies and a new unpatched one starts up17:02
cdentbut the nova process is the only one17:02
sean-k-mooneycfriesen: in that case build your continer form git repos instad of tarballs17:02
*** chhagarw has quit IRC17:03
sean-k-mooneycfriesen: that depends on how you run the container17:03
cdentcfriesen: it's not impossible to reload python code in the same process, but it is very icky17:03
sean-k-mooneyyour change inside a contaienr dont disappare on a docker reaster nova_compute17:03
sean-k-mooneycdent: and eventlet  monkeypatching makes it even harder17:04
cdentyes17:04
janguttercfriesen: docker containers ? I've hotpatched them, done 'docker commit' and 'docker restart'.17:04
janguttercfriesen: ugly, but hey, so am I.17:04
sean-k-mooneyjangutter: or docker exec then edit it and docker restart17:05
janguttersean-k-mooney: yep, that too.17:05
cfriesenjangutter: do you know how that behaves when the container is part of a pod that is part of a deployment or statefulset?17:05
sean-k-mooneycfriesen: it works fine in a pod17:05
janguttercfriesen: does the answer involve a singularity that slowly consumes all in its path?17:06
sean-k-mooneyyou are not deleting the contiaer so the deployment does not recreated the pod17:06
cfriesensounds promising...will have to try that.17:07
sean-k-mooneycfriesen: but modifying docker conatiner is generally considerd heresy. in k8s land its even more vilified17:07
janguttercfriesen: protip, pass '-u root' when doing the exec since you don't always have permissions.17:07
janguttercfriesen, sean-k-mooney: yeah, there's no guarantee any of the changes will persist or not. at best it's just something you do before you destroy the system.17:08
sean-k-mooneycfriesen: if you were using kolla-ansible they have a dev mode where the clone the git repo on the host and just bind mont into the container i think17:08
*** mvkr has quit IRC17:09
dansmithmriedem: am I missing what bug this actually fixes? https://review.openstack.org/#/c/647713/117:09
sean-k-mooneythe intended worflow being edit on host then docker restart nova_compute17:09
cfriesensean-k-mooney: yeah, that'd be cleaner17:10
cdentcfriesen: is this sort of live code tweaking a thing you find common?17:12
cdentI mean I can imagine it often enough in test settings, experiments, and the like17:13
cdentbut in a deployed world aren't the choices usually: observe, kill, make a new one?17:13
mnaserthere's not really any pythonic api to manage cells, right?17:14
mnaseror any api at all17:14
*** slaweq has quit IRC17:14
mnaserI am looking at adding multicell support in openstackansible, one of the things to introduce is the addition of some way to define cells17:15
cfriesencdent: this would be for tweaking stuff on lab systems.  I agree for areas where devstack is sufficient that'd be better.17:15
cdentcfriesen: I guess I was thinking a lab system is one of the main areas where "you have to make a new image, then tag it, and upload it to the repository, then tell helm to use the new image..." wouldn't be too much of a big deal, and you might have some simple(-ish) tooling to support it17:18
cdentI agree it is a PITA17:18
dansmithmnaser: you mean via the external API I assume? there isn't by design17:18
dansmithmnaser: or do you mean something like being able to import nova-manage and use its routines?17:19
mnaserdansmith: yeah.. or I was thinking maybe we could do something like.. import nova.cmd.manage; manage.add_cell() or whatever17:19
cfriesencdent: tool improvements would help, I agree.17:19
mnaser#2 (because ansible can just have python scripts run)17:19
dansmithmnaser: yeah, that could be a thing, but isn't currently17:19
mnaserfair enough, so for now probably best to stick to parsing CLI output17:19
dansmithmnaser: tbh, I think you probably don't want to import and run in your own namespace, since talking to cells requires pivoting global oslo.db state and other things17:20
mnaserdansmith: fair enough.. so probably better off just doing CLI operations17:21
dansmithmnaser: the cli commands aim to be pretty idempotent, but if we need --robot output formatting or something, then we should do that17:21
*** udesale has quit IRC17:23
openstackgerritChris Dent proposed openstack/nova master: WIP: Use update_provider_tree in vmware virt driver  https://review.openstack.org/65161517:26
*** priteau has quit IRC17:31
*** boxiang has quit IRC17:43
openstackgerritDakshina Ilangovan proposed openstack/nova-specs master: Nova LLC allocation - RMD plugin for RDT CAT  https://review.openstack.org/65123317:45
*** luksky has joined #openstack-nova17:47
*** boxiang has joined #openstack-nova17:48
*** ricolin has quit IRC17:49
mriedemdansmith: it's a perf improvement to avoid a call to get allocations for the instance created by the scheduler when we already have those in the Selection object in scope17:56
dansmithmriedem: ..right I got that ;)17:56
dansmithis that really substantial enough to backport?17:56
mriedemit's just new code in stein and missed the cutoff so it's not controversial imo17:58
mriedemwe wouldn't die without it no17:58
openstackgerritDakshina Ilangovan proposed openstack/nova-specs master: Nova local resource management that uses RMD  https://review.openstack.org/65113017:59
*** tjgresha has joined #openstack-nova17:59
*** tjgresha has quit IRC18:09
*** awalende has joined #openstack-nova18:11
*** awalende has quit IRC18:15
*** tosky has quit IRC18:21
*** wolverineav has quit IRC18:25
*** wolverineav has joined #openstack-nova18:25
*** wolverineav has quit IRC18:29
*** wolverineav has joined #openstack-nova18:29
*** ivve has joined #openstack-nova18:38
*** slaweq has joined #openstack-nova18:46
*** slaweq has quit IRC18:52
*** cdent has quit IRC18:54
openstackgerritDakshina Ilangovan proposed openstack/nova-specs master: Resource Management Daemon - Base Enablement  https://review.openstack.org/65113018:57
-openstackstatus- NOTICE: Restarting Gerrit on review.openstack.org to pick up new configuration for the replication plugin19:05
*** wolverineav has quit IRC19:05
*** wolverineav has joined #openstack-nova19:06
mriedemmelwitt: i re-read the counting quotas from placement spec for train again and noticed a few things that could be cleaned up https://review.openstack.org/#/c/645302/19:06
melwittmriedem: ok, thanks19:06
*** tssurya has quit IRC19:07
melwittmriedem: to your other comment (I'll reply on the review too), we're not counting unmigrated qfd instance mappings because we're falling back to legacy counting if unmigrated qfd instance mappings are detected19:07
melwitt(as opposed to counting unmigrated and being potentially wrong in the count)19:08
mriedemright i gathered that from the exchange between you and surya but i hadn't looked at the code yet that does the fallback logic19:09
*** wolverineav has quit IRC19:10
*** artom has quit IRC19:11
melwittoh, I see19:12
melwittI misunderstood what you meant by saying you needed to load the context of how it will be used19:12
openstackgerritDakshina Ilangovan proposed openstack/nova-specs master: Resource Management Daemon - Last Level Cache  https://review.openstack.org/65123319:20
*** eharney has quit IRC19:28
*** awalende has joined #openstack-nova19:28
*** tbachman has quit IRC19:29
efried_rollinmriedem: done19:37
*** efried_rollin is now known as efried19:37
*** owalsh has quit IRC19:43
*** wolverineav has joined #openstack-nova19:45
*** ralonsoh has quit IRC19:48
*** wolverineav has quit IRC19:49
*** owalsh has joined #openstack-nova19:50
melwittefried, mriedem: working on this old service uuid upgrade bug, IIUC because of this change https://review.openstack.org/620711 if we do a service delete followed by a service create, the running compute service will never create the resource provider and compute node again, for the same 'host', because it knows about it already in the RT19:51
*** tbachman has joined #openstack-nova19:51
melwitteven after another update_available_resource interval19:51
efriedhm, I thought someone fixed that recently.19:52
melwittthe func tests (written before that change landed) now fail because can't get the RP created again19:52
efriedoh, this is if you delete and recreate the service without actually stopping the running process?19:53
melwittI rebased the set today, so I should have all of the latest changes19:53
melwittcorrect19:53
efriedYes, this was definitely addressed recently, but I thought someone killed the change for reasons. Let me find it...19:53
mriedemhttps://review.openstack.org/#/c/641899/ ?19:53
efriedYup, that's the one. melwitt ^19:54
melwittlooking19:54
melwittI'm not even getting to that code though, it looks like that would at least try to create the provider19:55
*** amodi has quit IRC19:55
efriedmelwitt: Does that have the wrong bug number associated with it?19:55
efried(I'm asking, why didn't you find it if you were looking into this already?)19:56
efriedduplicate bugs?19:56
melwittoh they're saying after a service restart the RP create fails19:56
* efried shakes fist at PTL gods. "What have you done to me, that I care more about the paperwork than the solution??"19:57
melwittefried: oh sorry, I'm working on refreshing patches for an unrelated bug19:57
melwittand ran into this problem of the RP will never be created again while the service is running19:57
melwittbecause the func tests I'm working with are now failing because of it19:57
efriedI mean, it makes sense, because we have the provider tree cache, and no reason to think it has expired, so we never go looking for the provider to notice it's gone so we never create it.19:58
efriedThis is what SIGHUP was supposed to be for.19:58
melwittok, so it's a known thing that if an operator deletes and creates a service with the same hostname, they're supposed to SIGHUP now19:59
efriedAnd this would be a doc issue: "If you delete and recreate the service, SIGHUP (or restart ffs) your n-cpu process"19:59
efriedWell, I'm saying if it's not documented as such, that would be my first proposed solution. I'm not positive it's going to fix the problem (even when SIGHUP works, which it still doesn't afaik) but it'd be the first thing I'd try.19:59
mriedemfwiw we already have a note about that in the API reference https://developer.openstack.org/api-ref/compute/?expanded=delete-compute-service-detail#delete-compute-service19:59
melwittok. I can simulate that in the test, but wanted to mention it in case it wasn't desired/expected20:00
melwittthanks20:00
efriedcool, the doc actually says to stop the thing, which makes freakin sense to me.20:00
efriedMaybe I'm being too simplistic in my thinking20:01
efriedbut how does an operator expect "delete a thing but keep it running" to ever work?20:01
*** ivve has quit IRC20:01
melwittno, it's fine, I just saw a change and didn't have the context about it20:01
melwittwell, the delete it and create it again, so they expect it to be running after they create it, in this scenario20:02
efriedsorry, tbc I'm not griping at you; I guess I'm kind of wtf-ing that there's a bug about this.20:02
efriedPerhaps we should have delete kill the service20:02
efriedI think that may be what cdent was suggesting in the above patch20:02
melwittI can't remember why operators have done that, something to do with an upgrade. cfriesen ran into it before I think20:03
efried...or make the delete operation fail if the service is running, to force the operator to do it.20:03
melwitt(delete service, create service, for same hostname)20:03
efriedOh, I'm *sure* there's a good reason to do that ^20:04
efried:)20:04
efriedbut expecting the running process to survive intact and work properly through it...20:04
efriedperhaps it used to work by pure luck and now they're facing RBB.20:05
cfriesenI think we probably hit it during upgrade...our upgrade mechanism was to delete the standby controller, then reinstall it with the new load (and the same hostname as before), then migrate the DB over and cut over to the new controller.20:06
melwittcfriesen: that sounds like what I recall20:07
cfriesenhmm..that wouldn't delete the nova-compute service though.20:07
*** wolverineav has joined #openstack-nova20:08
*** owalsh has quit IRC20:08
melwittcfriesen: yeah this was deleting the nova-compute service for a host, then recreating it. deleting the nova-compute service record would kill the compute node record too20:08
*** owalsh has joined #openstack-nova20:08
melwittand you're saying your upgrade routine would not do that20:08
*** igordc has joined #openstack-nova20:08
cfriesenI don't think so...trying to find the context for https://bugs.launchpad.net/nova/+bug/176455620:10
openstackLaunchpad bug 1764556 in OpenStack Compute (nova) ""nova list" fails with exception.ServiceNotFound if service is deleted and has no UUID" [Medium,In progress] - Assigned to melanie witt (melwitt)20:10
melwittcfriesen: it's ok, don't spend time on it. we were just talking about the whole service delete and create thing. behavior changed semi recently20:11
melwittand I thought I remembered you might have done something like that in the past20:11
cfriesenokay, so it looks like for that bug we *did* delete a compute node while on Newton, then migrated to Pike, then created a new node with the same name. May have been an artificial test though, not actually required for upgrade.20:11
cfriesenupgraded to Pike, rather20:12
melwittgotcha20:12
mriedemthe delete compute service while it's still running was never really thought out i don't think20:16
mriedemwe've only semi recently tried to shore up a lot of that nonsense20:16
mriedemit's only been noticed as more of a problem since we started building onto it with things like host mappings and resource providers20:16
* melwitt nods20:17
mriedemi.e. this is semi recent https://github.com/openstack/nova/blob/d42a007425d9adb691134137e1e0b7dda356df62/nova/api/openstack/compute/services.py#L24720:17
mriedemand this https://github.com/openstack/nova/blob/d42a007425d9adb691134137e1e0b7dda356df62/nova/api/openstack/compute/services.py#L27020:17
mriedemand this https://github.com/openstack/nova/blob/d42a007425d9adb691134137e1e0b7dda356df62/nova/api/openstack/compute/services.py#L27520:17
melwittah yeah, I remember that first one20:18
*** awalende has quit IRC20:19
*** awalende has joined #openstack-nova20:19
*** slaweq has joined #openstack-nova20:23
openstackgerritMerged openstack/nova stable/stein: doc: Capitalize keystone domain name  https://review.openstack.org/65060020:23
openstackgerritMerged openstack/nova stable/stein: Add functional regression test for bug 1669054  https://review.openstack.org/64931920:24
openstackbug 1669054 in OpenStack Compute (nova) stein "RequestSpec.ignore_hosts from resize is reused in subsequent evacuate" [Medium,In progress] https://launchpad.net/bugs/1669054 - Assigned to Matt Riedemann (mriedem)20:24
*** awalende has quit IRC20:24
openstackgerritMerged openstack/nova stable/stein: doc: Fix openstack CLI command  https://review.openstack.org/64841220:24
openstackgerritmelanie witt proposed openstack/nova master: Add functional recreate test for bug 1764556  https://review.openstack.org/56204120:28
openstackbug 1764556 in OpenStack Compute (nova) ""nova list" fails with exception.ServiceNotFound if service is deleted and has no UUID" [Medium,In progress] https://launchpad.net/bugs/1764556 - Assigned to melanie witt (melwitt)20:28
openstackgerritmelanie witt proposed openstack/nova master: Add functional regression test for bug 1778305  https://review.openstack.org/58240720:28
openstackgerritmelanie witt proposed openstack/nova master: Don't generate service UUID for deleted services  https://review.openstack.org/58240820:28
openstackbug 1778305 in OpenStack Compute (nova) "Nova may erronously look up service version of a deleted service, when hostname have been reused" [Medium,In progress] https://launchpad.net/bugs/1778305 - Assigned to melanie witt (melwitt)20:28
*** wolverineav has quit IRC20:31
openstackgerritChris Friesen proposed openstack/nova stable/rocky: Add missing libvirt exception during device detach  https://review.openstack.org/65163720:31
*** priteau has joined #openstack-nova20:33
openstackgerritChris Friesen proposed openstack/nova stable/queens: Add missing libvirt exception during device detach  https://review.openstack.org/65163920:34
*** phasespace has joined #openstack-nova20:36
openstackgerritChris Friesen proposed openstack/nova stable/pike: Add missing libvirt exception during device detach  https://review.openstack.org/65164220:36
*** wolverineav has joined #openstack-nova20:40
*** wolverineav has quit IRC20:43
*** wolverineav has joined #openstack-nova20:43
*** ivve has joined #openstack-nova20:48
*** priteau has quit IRC20:48
*** wolverineav has quit IRC20:48
*** mvkr has joined #openstack-nova20:52
openstackgerritMatt Riedemann proposed openstack/nova master: Use InstanceList.get_count_by_hosts when deleting a compute service  https://review.openstack.org/65164720:54
*** nicolasbock has quit IRC21:05
*** wolverineav has joined #openstack-nova21:12
openstackgerritMatt Riedemann proposed openstack/nova master: Add archive_deleted_rows wrinkle to cross-cell functional test  https://review.openstack.org/65165021:12
*** nicolasbock has joined #openstack-nova21:13
openstackgerritMatt Riedemann proposed openstack/nova master: Add archive_deleted_rows wrinkle to cross-cell functional test  https://review.openstack.org/65165021:15
*** slaweq has quit IRC21:21
*** wolverineav has quit IRC21:24
*** ivve has quit IRC21:25
*** wolverineav has joined #openstack-nova21:25
*** wolverineav has quit IRC21:26
*** wolverineav has joined #openstack-nova21:26
openstackgerritMatt Riedemann proposed openstack/nova-specs master: FUP for I68498afd481f7291a6102928d7999b4be49ded7a  https://review.openstack.org/65165321:33
*** eharney has joined #openstack-nova21:37
*** slaweq has joined #openstack-nova21:38
*** mriedem has quit IRC21:40
*** slaweq has quit IRC21:42
*** wolverineav has quit IRC21:46
openstackgerritMerged openstack/nova stable/stein: Override the 'get' method in DriverBlockDevice class  https://review.openstack.org/64764621:47
openstackgerritMerged openstack/nova stable/stein: Don't warn on network-vif-unplugged event during live migration  https://review.openstack.org/65006021:47
*** wolverineav has joined #openstack-nova21:48
*** wolverineav has quit IRC21:52
openstackgerritMerged openstack/nova stable/stein: libvirt: disconnect volume when encryption fails  https://review.openstack.org/65093121:55
openstackgerritMerged openstack/nova stable/stein: Move create of ComputeAPI object in websocketproxy  https://review.openstack.org/64937422:01
*** eharney has quit IRC22:06
*** rcernin has joined #openstack-nova22:06
*** tjgresha has joined #openstack-nova22:15
*** luksky has quit IRC22:17
*** mlavalle has quit IRC22:19
*** wolverineav has joined #openstack-nova22:25
*** tosky has joined #openstack-nova22:26
*** wolverineav has quit IRC22:31
*** betherly has joined #openstack-nova22:32
openstackgerritColleen Murphy proposed openstack/nova stable/rocky: Move create of ComputeAPI object in websocketproxy  https://review.openstack.org/64937522:35
*** betherly has quit IRC22:37
*** munimeha1 has quit IRC22:41
*** tosky has quit IRC22:47
*** slaweq has joined #openstack-nova22:49
*** whoami-rajat has quit IRC22:51
*** tkajinam has joined #openstack-nova22:53
*** slaweq has quit IRC22:53
*** wolverineav has joined #openstack-nova23:06
*** wolverineav has quit IRC23:11
*** betherly has joined #openstack-nova23:12
*** betherly has quit IRC23:17
*** david-lyle has joined #openstack-nova23:36
*** dklyle has quit IRC23:36
*** david-lyle has quit IRC23:46
*** artom has joined #openstack-nova23:48
openstackgerritArtom Lifshitz proposed openstack/nova master: Revert "Wait for network-vif-plugged on resize revert"  https://review.openstack.org/63939623:51
openstackgerritArtom Lifshitz proposed openstack/nova master: [WIP] Revert resize: wait for external events in compute manager  https://review.openstack.org/64488123:51
*** rcernin has quit IRC23:52
*** owalsh has quit IRC23:57

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!