Earlier  
Posted Nick Remark
#openstack-nova - 2017-02-09
15:05:10 mordred sdague: what confuses me more is that they seem to be getting availability_zone back in their response dict
15:05:11 sdague mordred could probably answer that keystoneauth1 assumption best
15:05:13 nicolasbock cdent, ok
15:05:24 sdague mordred: from what provider?
15:05:39 sdague mordred: that's definitely no where near upstream code
15:06:00 mordred sdague: unknown. I'll be asking- and telling them I will not support az for that resource
15:06:08 mordred sdague: what keystoneauth assumption?
15:06:09 EmilienM cdent, sdague: http://logs.openstack.org/15/424915/13/check/gate-puppet-openstack-integration-4-scenario001-tempest-centos-7/42fa9b9/logs/keystone-resources.txt.gz
15:06:39 cdent EmilienM: but at what time is that list made?
15:06:43 mordred yes. keystoneauth1 will not get a new token if the current token is valid
15:06:48 EmilienM cdent: after CI run
15:06:54 EmilienM cdent: it's in post-ci thing, when we gather logs
15:06:57 cdent if it is late in the process then it doesn't tell us anything
15:06:59 EmilienM cdent: so wayyyyy after tempest ran
15:07:11 cdent if the catalog doesn't have placement in it when n-cpu starts up, then boom?
15:07:24 EmilienM that's a good question ^
15:07:38 EmilienM because nova-cpu starts BEFORE httpd, which means before endpoints/services are created
15:08:00 mordred that seems like ordering you'll need to change
15:08:07 EmilienM so if nova-cpu is not able to retry by itself, indeed this is a problem
15:08:11 mordred as more and more things decide to use the catalog to get references to each other
15:08:12 EmilienM mordred: I disagree
15:08:23 EmilienM mordred: nova compute should be able to retry by itself
15:09:04 sdague EmilienM: you really need to have layed out your service catalog before any services start
15:09:05 EmilienM and placement registration is already retrying in nova-compute (dan wrote it iirc)
15:09:07 mordred EmilienM: but if the catalog is required to find out where other apis are, then one should register services with keystone before starting dependent services no?
15:09:14 sdague mordred: ++
15:09:38 dansmith agree, catalog should be available first
15:09:54 EmilienM ok I disagree with your approach but I'll follow your suggestion and tell nova compute to start after
15:10:08 sdague this is a pretty basic flow assumption
15:10:08 EmilienM I'll let you know how it works very shortly
15:10:26 sdague bring up keystone, create all service users, create all endpoint definitions, bring up rest of services
15:10:48 dansmith just like start apache after you have network up so it can bind to addresses, etc
15:11:07 EmilienM sdague: ok, let me change that now.
15:11:11 mordred so - that brings to mind a question though...
15:11:12 mriedem johnthetubaguy: thanks for running the meeting, looks like it was a short one
15:11:14 openstackgerrit Jeremy Liu proposed openstack/nova master: [3/3]Replace six.iteritems() with .items() https://review.openstack.org/415080
15:11:32 mordred what happens when all the service apis run in apache?
15:11:55 EmilienM mordred: nova-api in WSGI / apache is not supported
15:12:02 sdague mordred: what's the question?
15:12:07 EmilienM mordred: they suggested me to revert what we did in TripleO and use eventlet
15:12:09 mordred I know - but what about when we get to the point where it is?
15:12:21 sdague mordred: I don't think that changes the flow
15:12:26 mordred so that there isn't really a possibility of starting api endpoints in a particular order
15:12:29 mordred sdague: no?
15:12:30 EmilienM in the case of nova compute, no
15:12:35 mordred oh. duh. nevermind
15:12:39 sdague mordred: you can totally enable just keystone
15:12:44 cdent keystone becomes a...keystone
15:12:46 sdague do all it's stuff
15:12:51 sdague then bring up everything else
15:13:03 mordred yah - nevermind - only on second coffee
15:13:04 mordred :)
15:13:05 sdague heh
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

Earlier   Later