Earlier  
Posted Nick Remark
#openstack-nova - 2017-02-09
15:13:55 sdague mordred: yeh, even in those cases, you'll still need a keystone bootstrapping phase. I can't imagine that ever goes away
15:15:49 cdent TIL
15:17:30 openstackgerrit John Garbutt proposed openstack/nova master: Assume neutron port_binding extensions enabled https://review.openstack.org/357726
15:17:35 johnthetubaguy mriedem: no worries
15:18:16 jroll johnthetubaguy: we have a "Virt and Metal in the same region" topic in our ptg list, feels like that should be a nova topic, wdyt?
15:18:50 johnthetubaguy jroll: feels like a joint topic
15:19:05 jroll johnthetubaguy: maybe, I know it's mostly nova issues though
15:19:12 johnthetubaguy jroll: oh, well more nova than ironic though
15:19:39 johnthetubaguy jroll: has anyone got a concrete list of issues yet, thats what I was struggling with
15:21:00 jroll johnthetubaguy: just that etherpad that was going around
15:21:08 jroll idk how concrete things are now
15:21:32 johnthetubaguy jroll: thats probably the list I dreamt up one warning, yeah.
15:23:00 openstack Launchpad bug 1630600 in OpenStack Compute (nova) "swap volume intermittently fails with "libvirtError: block copy still active: domain has active block job"" [Medium,In progress] - Assigned to Lee Yarwood (lyarwood)
15:23:00 mriedem lyarwood: is this still a valid bug https://bugs.launchpad.net/nova/+bug/1630600 ?
15:25:56 openstack Launchpad bug 1663163 in OpenStack Compute (nova) "Improper prompt when update existed resource class" [Undecided,In progress] - Assigned to Eric Xie (eric-xie)
15:25:56 macsz cdent: found a bug report that was missing a placement tag, maybe you want to take a look: https://bugs.launchpad.net/nova/+bug/1663163
15:26:07 lyarwood mriedem: that should be resolved by https://review.openstack.org/#/c/399735/
15:26:25 cdent macsz: thanks for letting me know, looking now
15:27:16 kashyap lyarwood: Was about to ask if you backported it to stable/newton, you did indeed :-)
15:27:43 mriedem lyarwood: can we duplicate the bug then to close it out?
15:27:55 lyarwood mriedem: yup I'll do that now
15:28:04 mriedem thanks
15:28:09 mriedem i'm reviewing that backport right now too
15:28:16 mriedem had a customer hit that in mitaka
15:28:19 ianychoi mriedem oh hi. I am from I18n team. I am calling you.. since I saw your message too late
15:28:52 mriedem lyarwood: i also remember you triaged a bug yesterday related to swap volume, but it was a failure in libvirt (the reporter was using trusty) - and you pointed out a fix in upstream libvirt, that's in xenial, do you happen to know what i'm talking about?
15:28:54 lyarwood mriedem: yeah same, backporting this all the way back is soooooo much fun
15:29:00 mriedem ianychoi: hi
15:29:07 lyarwood mriedem: yeah I do
15:29:15 ianychoi mriedem, yep ping me again if you finish the current converation :)
15:29:27 mriedem ianychoi: it's my understanding that nova won't have translations performed for ocata?
15:29:41 mriedem ianychoi: i just wanted to confirm so that we don't hold up our rc2 for translations that aren't coming
15:30:49 ianychoi mriedem, thanks a lot for raising this issue. Let me tell more details on this issue.
15:31:44 openstack bugzilla.redhat.com bug 1202704 in libvirt "libvirt doesn't deal with the block job info correctly when fail to do active blockcommit" [High,Closed: errata] - Assigned to pkrempa
15:31:44 mriedem lyarwood: was it this? https://bugzilla.redhat.com/show_bug.cgi?id=1202704
15:31:57 jroll johnthetubaguy: so anyway, do you think we have enough info to drop some topics on nova ptg agenda?
15:32:01 mriedem the customer is running libvirt 1.2.17 on one compute node and 2.0 on another so that should be fixed for them
15:32:29 ianychoi Previously, i18n team dealt all the translations with so many number of projects but i18n team felt that there is less attention on server projects rather than user-facing projects such as horizon and horizon plugin projects. So I18n team decided to more focus on user facing projects during Ocata cycle.
15:32:33 johnthetubaguy jroll: I think we should put it on there either way, I should think about going to dig into that
15:32:58 jroll johnthetubaguy: alright, sounds good
15:33:06 lyarwood mriedem: yeah that's it
15:33:09 EmilienM cdent, sdague: my actions to follow your suggestion https://review.openstack.org/#/q/topic:bug/1663273
15:33:22 lyarwood mriedem: sorry launchpad search is fscking awful
15:33:32 mriedem lyarwood: yeah i know :)
15:33:35 ianychoi So.. I will deal with stable/ocata branch creation for Ocata branch.. but I am not currently pretty sure who wants to deal with translation bug fixes for server projects (e.g., nova)
15:33:39 mriedem i found ^ via the internal email thread i'm on
15:33:39 cdent EmilienM, cool, will look in a sec
15:34:04 ianychoi This is why I am delaying to create stable versions in Zanata and syncing with translation for stable branches
15:34:05 jroll johnthetubaguy: I have some WIP topics at line 81 btw, if you're curious https://etherpad.openstack.org/p/nova-ptg-pike
15:34:07 mriedem ianychoi: do you mean branch creation in zenat?
15:34:10 mriedem *zenata?
15:34:23 dansmith EmilienM: wouldn't it be better to make sure all services run after that point?
15:34:35 ianychoi mriedem, both: stable version craeation on Zanata & translation sync job for stablr branch
15:34:47 mriedem ok
15:34:50 EmilienM dansmith: we can't make this change at this stage of this cycle, we'll only do nova compute for now and if things work let's ship it in ocata and improve it in pike
15:34:56 sdague dansmith: ++
15:35:01 kashyap mriedem: I'll assume that fix wasn't backported to Mitaka, as it's security-only. Hence you must've down a downstream backport
15:35:20 mriedem kashyap: i think the L3 guys are working with the customer on the backport to their systems on mitaka
15:35:27 mriedem which....they could have screwed up for all i know
15:35:31 mriedem i've been trying to stay out of it
15:35:39 EmilienM dansmith: what you're asking has too much impact on different areas and we need to address it without stress & pressure (outside release week)
15:35:51 ianychoi mriedem, I am responsible for submitting a patch like https://review.openstack.org/#/c/429409/ to support translation sync with stable branches also the cration for stable versions in Zanata
15:35:55 sdague mordred: did you figure out what cloud provided the keystone / az bug?
15:35:58 ianychoi (as I18n PTL)
15:36:04 sdague mordred: I mean keypair
15:36:20 mriedem ianychoi: ok
15:36:22 dansmith EmilienM: your call, but just seems like a recipe for other issues
15:36:31 ianychoi mriedem, by the way, auggy is still I18n - nova cross project liaison? https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n
15:37:14 EmilienM dansmith: in other words: "yes you're right but I don't have the time to do it now, the list of items to address your requests is to big if we want to release Ocata before the deadline"
15:37:29 ianychoi I know that some information on https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n seems old. I would like to update it as much as possible now
15:38:08 mriedem auggy: are you still i18n liaison?
15:38:25 mordred sdague: just responded to the bug asking that question
15:38:48 openstackgerrit John Garbutt proposed openstack/nova master: Use admin context to create neutron ports https://review.openstack.org/357540
15:40:20 ianychoi Hmm.. no response now but so fine, since we are living with different timezone :)
15:41:11 ianychoi mriedem, then.. would it be fine if I create stable-ocata version in Zanata and support translation sync job with stable/ocata branch around release date?
15:41:44 ianychoi If there would be more concern (e.g., more early period), please tell me.
15:44:33 cdent macsz: looks like Eric is fixing that himself, yeah? Ought to be a one line fix (not counting tests). Thanks for finding that.
15:45:38 macsz macsz: yeah, just wanted to keep you posted, as the timeline for fixing anything crucial (if it has any chance to land for RC2) is rather short
15:46:43 cdent macsz: Do you think that should warrant a backport? It's not breaking anything too badly, is it?
15:48:18 mordred sdague: I have an unconfirmed hunch that it's fujitsu - the bug reporter has some other github repos related to the fujitsu-k5 cloud
15:48:27 mordred sdague: https://github.com/JonTheNiceGuy/k5-ansible-modules "As K5 is Availability Zone centric new modules were created to communicate with K5 which then bypass limitations in the Ansible Openstack os modules."
15:48:35 mriedem ianychoi: i'm fine with that, we just won't hold up the nova ocata rc2 on translations
15:48:36 macsz cdent: it isn't breaking anything, to be frank, rather just the error is not stated correctly, but it is also a really small change with impact close to 0
15:48:54 sdague mordred: ok, so crazy upstream fork that does something different with az
15:49:00 mordred yup
15:49:05 sdague I bet they are doing one of those fake federated models
15:49:15 sdague where the az is really a whole other openstack deploy
15:49:22 cdent macsz: I'm not the expert on these things (/me looks at mriedem ) but I reckon that breaking something is probably a reasonab bar at this point?
15:49:33 macsz cdent: i guess
15:49:45 macsz cdent: well, let's just leave it :)
15:49:50 mordred sdague: yah. there are people who can't get past the fact that in openstack the word "region" means what the word "az" means in amazon
15:50:02 mordred like it REALLY drives them completely batty
15:50:29 ianychoi mriedem, I see thanks! I will create stable-ocata version for nova and support translation sync around your rc3 or final release, but it would be much better if nova-i18n liaison will notify rc3 and final release to me :)
15:51:03 sdague mordred: yeh, well, we do have a lot of non overlapping grouping constructs that are weird
15:51:10 mordred we do for sure
15:51:18 mordred but making a fork which redefines them doesn't really help anybody
15:51:24 sdague mordred: ++
15:53:54 mriedem ianychoi: to be clear, we have rc1 now, and are working to rc2 by 2/16
15:54:02 mriedem ianychoi: so i don't plan on an rc3
15:55:07 ianychoi mriedem, thanks than I will consider with nova rc2 rather than rc3

Earlier   Later