| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2020-04-15 | |||
| 12:28:56 | bauzas | good luck with that | |
| 12:29:37 | bauzas | gibi: no, please, keep looking at the top list, I'll do something else with bugs that is important close to RC1 | |
| 12:30:12 | bauzas | gibi: like i said, I've stopped a couple of times some bugs that were in progress and were crucial because they were fixing a regression | |
| 12:30:30 | bauzas | we were just missing them since someone proposed a patch and didn't yell it | |
| 12:30:39 | gibi | bauzas: OK. I will look at the top for the next 30 minutes, then I have to jump on a call | |
| 12:30:59 | bauzas | as soon as someone proposes a patch, then the related bugs disappear from our radara | |
| 12:30:59 | gibi | I will let you know when I released the semaphor | |
| 12:31:02 | bauzas | radar* | |
| 12:31:19 | gibi | bauzas: yes, good point. If you have a good query for those bugs then please share | |
| 12:31:31 | bauzas | gibi: easy peasy, sec | |
| 12:34:00 | bauzas | gibi: https://frama.link/Z-EVGtyx | |
| 12:34:55 | bauzas | enjoy the list, 112 potential regressions :p | |
| 12:35:25 | bauzas | maybe 20 if we only consider the last 6 months | |
| 12:36:08 | bauzas | those bugs are in general written by developers who found a bug | |
| 12:36:34 | bauzas | whether the issue is new (hence a regression) or always existing, that's the crux of the problem :) | |
| 12:38:37 | openstack | Launchpad bug 1872385 in OpenStack Compute (nova) "delete sub resource provider in tree" [Undecided,In progress] - Assigned to Wenping Song (wenping1) | |
| 12:38:37 | bauzas | gibi: like, first case https://bugs.launchpad.net/nova/+bug/1872385 | |
| 12:39:06 | bauzas | yay... | |
| 12:40:22 | bauzas | gibi: we don't have yet ussuri-rc-potential tag ? | |
| 12:40:35 | sean-k-mooney | not offically but im already using it | |
| 12:40:42 | sean-k-mooney | i was going to go update the tags | |
| 12:41:13 | sean-k-mooney | sorry not the rc on i am using the backport potential one | |
| 12:41:20 | bauzas | sean-k-mooney: just saying https://bugs.launchpad.net/nova/+bugs?field.tag=ussuri-rc-potential | |
| 12:41:30 | bauzas | sean-k-mooney: that's different | |
| 12:41:35 | sean-k-mooney | yes it is | |
| 12:41:49 | bauzas | sean-k-mooney: you shouldn't use this tag (backport) yet | |
| 12:41:50 | sean-k-mooney | the cyborg bug is not an rc candiate | |
| 12:41:57 | sean-k-mooney | so i notice that both were missing | |
| 12:44:15 | bauzas | sean-k-mooney: sorry I don't get you ? | |
| 12:44:52 | gibi | bauzas: I did not needed the tag yet | |
| 12:45:09 | gibi | bauzas: I thought it is created when first needed | |
| 12:45:12 | sean-k-mooney | from https://bugs.launchpad.net/nova/+manage-official-tags | |
| 12:45:25 | gibi | bauzas: is there another way to pre-create a tag? | |
| 12:45:29 | sean-k-mooney | i have moved ussuri-backport-potential to offical | |
| 12:45:50 | sean-k-mooney | but i cant add ussuri-rc-potential for some reason | |
| 12:46:11 | bauzas | gibi: no, you just use it on purpose but then you can promote it 'official' | |
| 12:46:14 | gibi | me neither | |
| 12:46:29 | bauzas | gibi: it will then raise the visibility | |
| 12:46:39 | gibi | OK | |
| 12:46:40 | bauzas | hold on, doing it for one bug | |
| 12:47:07 | bauzas | gibi: there https://bugs.launchpad.net/nova/+bugs?field.tag=ussuri-rc-potential | |
| 12:47:25 | gibi | thanks | |
| 12:47:26 | bauzas | gibi: look at the right panels, you can see the list of tags | |
| 12:47:41 | bauzas | and there is one link for 'edit official tags' | |
| 12:47:55 | slaweq | gibi: thx a lot for checking this grenade issue | |
| 12:47:57 | sean-k-mooney | https://bugs.launchpad.net/nova/+manage-official-tags | |
| 12:47:58 | bauzas | which leads to https://bugs.launchpad.net/nova/+manage-official-tags | |
| 12:48:04 | bauzas | jinx | |
| 12:48:16 | gibi | OK, thanks I made it official | |
| 12:48:21 | bauzas | and then, I'm adding ussuri-rc-potential to the left list | |
| 12:49:08 | gibi | slaweq: I hope melwitt has some future ideas. she looked a lot at this bug | |
| 12:49:59 | bauzas | sean-k-mooney: gibi: the ussuri-backport-potential is mostly used for knowing whether it's a good backport candidate after GA | |
| 12:50:12 | sean-k-mooney | bauzas: yep i know | |
| 12:50:24 | bauzas | but we should iterate over the list of ussuri-rc-potential before and after RC1 | |
| 12:50:43 | bauzas | until we get 0 candidates | |
| 12:50:46 | sean-k-mooney | bauzas: i wanted to also flag that this was not intended to be fixed in the rc | |
| 12:50:57 | bauzas | the -backport tag ? yes | |
| 12:51:03 | bauzas | was that a question ? | |
| 12:51:30 | bauzas | like I said earlier "(14:49:59) bauzas: sean-k-mooney: gibi: the ussuri-backport-potential is mostly used for knowing whether it's a good backport candidate after GA" | |
| 12:51:32 | sean-k-mooney | yep im going to be reuploading it later today but i do not intend the patch to merge untill after ussuri is released then ill backport it | |
| 12:51:35 | bauzas | *after GA* | |
| 12:55:32 | bauzas | sean-k-mooney: a cyborg patch you mean ? I'm confused again :) | |
| 12:57:44 | gibi | bauzas: I'm releasing the bug lock for now, need to jump on a call | |
| 12:58:18 | bauzas | gibi: ack | |
| 13:08:50 | openstack | Launchpad bug 1863038 in OpenStack Compute (nova) "Nova need to consider ironic node as 'host'" [Undecided,New] | |
| 13:08:50 | gibi | sean-k-mooney: do you have a feeling about https://bugs.launchpad.net/nova/+bug/1863038 ? For me it seems that the routed network feautre was never considered ironic in the first place. | |
| 13:10:48 | bauzas | routed networks aren't a thing yet, right? | |
| 13:13:40 | gmann | stephenfin: chekcing.. | |
| 13:16:07 | gibi | bauzas: it works, in a narrow case | |
| 13:16:17 | bauzas | kk | |
| 13:16:21 | gibi | bauzas: when a port is pre-create with ip_allocation=deferred config | |
| 13:16:22 | bauzas | I missed that then | |
| 13:16:46 | gibi | for that case there was no need for nova change | |
| 13:17:19 | gibi | iff every network has a segment for every compute | |
| 13:18:24 | gibi | but overall you are right there is no real, good, tested routed net support in nova | |
| 13:22:06 | gmann | stephenfin: replied. please check | |
| 13:22:18 | gmann | stephenfin: https://review.opendev.org/#/c/662968/9 | |
| 13:23:10 | bauzas | gibi: ahah, now I understand why I never heard of this as 'implemented' | |
| 13:23:18 | bauzas | it was all proxied to neutron then | |
| 13:23:22 | bauzas | gotcha | |
| 13:24:22 | gibi | sean-k-mooney: bauzas: we will talk about route net support in nova during the PTG so this ironic case might be also a question for that discussion | |
| 13:25:32 | sean-k-mooney | sorry was distracted ill read scrollback | |
| 13:28:05 | sean-k-mooney | bauzas: well we jsut dont have schduling support | |
| 13:29:18 | sean-k-mooney | you can sort of force it to work by mapping AZs to routed segments but that is a pain and a hack | |
| 13:29:56 | sean-k-mooney | if you map an AZ to a segment then the fact we dont live migrate across AZs by default make it work fine provided you use ip_allocaiton=deffered | |
| 13:30:44 | efried | sean-k-mooney, gibi: I sure would like to see the provider yaml feature land. It's something we've talked about for years and years, and it's the first step toward being able to do PCI passthrough whitelisting+configuration properly. If you're still planning to represent PCI devices as child providers _ever_, you're going to want it or something like it. And the current work is *so* close. | |
| 13:31:19 | efried | tbc, my position on this is not related to employer, but to what I see as the right direction for nova | |
| 13:31:42 | sean-k-mooney | efried: yep althouhg i dont really like how we are doing to modeling if we are going to use it for pci if im being totally honest | |
| 13:31:54 | sean-k-mooney | that said its not awful either | |
| 13:32:09 | sean-k-mooney | its just missing the corralation to the actul devices | |
| 13:32:18 | sean-k-mooney | which could be added in a later schema version | |
| 13:32:35 | efried | oh, as written it's not ready for PCI yet, for sure. | |
| 13:33:04 | efried | we dialed back to the bare bones to get a mvp that would fit in a cycle | |
| 13:33:52 | sean-k-mooney | efried: my alternitve spec for this feature start with pci modeling as the MVP with what the current feature does as out of scope | |
| 13:34:02 | sean-k-mooney | well kind of | |
| 13:34:14 | sean-k-mooney | anyway i do think its worth completing give how close it is | |
| 13:34:42 | sean-k-mooney | efried: would you remind removing your -2 on the bottom patch and maybe gibi could add his | |
| 13:35:06 | sean-k-mooney | so that we dont need to find you to do that when we get to victoria | |
| 13:35:16 | bauzas | stephenfin: i'd appreciate some reviews of https://review.opendev.org/#/c/712741/2 btw. | |
| 13:35:38 | efried | oh, I have a -2? Fixing... | |