Earlier  
Posted Nick Remark
#openstack-nova - 2017-02-01
16:55:27 dansmith I already have the patch up
16:55:32 bauzas oh, nice
16:55:35 dansmith WIP, so don't go look yet
16:55:43 bauzas please be a gentleman, so I could CC it :)
16:56:27 dansmith wat?
16:57:32 dansmith oh fuck. that breaks every api samples test.. cripes.
17:06:01 bauzas dansmith: cells meeting or should we leave you having fun with api sample tests ?
17:06:12 dansmith bauzas: we just had it and you didn't show up
17:06:27 dansmith so we adjourned to do work
17:06:48 bauzas heh
17:11:41 mriedem so i can't figure this out,
17:11:42 mriedem https://github.com/openstack/nova/blob/master/nova/tests/unit/conductor/test_conductor.py#L1513
17:11:53 mriedem i changed that to self.assertEqual(3, build_and_run_instance.call_count)
17:11:59 mriedem and it always fails saying it's only called once
17:12:04 mriedem but there are 3 build requests in that test
17:12:35 mriedem as far as i can tell, things should be peachy
17:13:13 edleafe jaypipes: are you working on https://review.openstack.org/#/c/404472/, or do you want me to fix the tests?
17:14:55 bauzas mriedem: but we only schedule once with 3 requests in it, right ? https://github.com/openstack/nova/blob/master/nova/tests/unit/conductor/test_conductor.py#L1512
17:15:44 mriedem bauzas: it's asserting this is called https://github.com/openstack/nova/blob/d308d1f70e7e840b1b0c8f4307998d89f9a5ddff/nova/conductor/manager.py#L959
17:15:48 mriedem which is in a for loop
17:15:53 mriedem over the list of build requests
17:15:59 mriedem of which there are 3
17:16:07 mriedem so unless something is failing and making it continue before that for 2 of them, i'm lost
17:19:18 bauzas mriedem: correct me if I'm wrong, but we're only passing one request_spec ?
17:19:47 bauzas so the zip thing would only return one tuple
17:20:56 bauzas mriedem: yup, we're only passing one of those https://github.com/openstack/nova/blob/master/nova/tests/unit/conductor/test_conductor.py#L1414-L1415
17:22:30 bauzas mriedem: so if you wanna make sure you have 3 calls, just add 2 new request_specs in the params dict
17:23:03 jaypipes edleafe: yeah, I'm working on it.
17:23:24 edleafe jaypipes: cool - didn't want it to languish if you were busy
17:23:38 jaypipes edleafe: yeah, sorry, meeting hell day..
17:28:20 mriedem bauzas: ah beautiful
17:28:22 mriedem thanks
17:28:55 openstackgerrit Dan Smith proposed openstack/nova: Remove pre-cellsv2 short circuit in instance get https://review.openstack.org/427782
17:29:03 bauzas \o/
17:30:20 breitz anybody use and IDE like pycharm to debug nova with? I'm trying but failing to find the magic to make it all work
17:30:46 dtp dansmith melwitt you guys need anything?
17:31:03 dansmith dtp: own any guns?
17:31:19 dtp no :( but have been thinking about it lately
17:31:25 dansmith dtp: then, no.
17:31:27 dansmith heh
17:31:29 dtp :)
17:32:11 mriedem dtp: review these? https://review.openstack.org/#/q/topic:man+project:openstack/nova+status:open
17:32:20 dtp ok
17:33:09 bauzas breitz: I think we have something about that
17:33:12 bauzas in our dev doc
17:33:25 bauzas breitz: but tbh, I just pdb when I want to introspect
17:33:36 marst breitz: what's failing?
17:33:40 mriedem LOG.error is my pdb
17:33:50 breitz thats what I do (pdb) but was looking for getting an IDE working.
17:33:55 bauzas yeah found http://docs.openstack.org/developer/nova/development.environment.html#using-a-remote-debugger
17:33:59 bauzas breitz: ^
17:34:29 bauzas mriedem: sometimes you need something more dynamic :p
17:34:57 bauzas like "oh shit, I knew that, I need to run again to see the next call"
17:35:05 mriedem LOG.error(locals())?!
17:35:35 breitz thanks for the link - I'll read through that (some of which I've followed). Basically I can get pycharm to connect to the remote - but I can't get any breakpoints in nova-compute or any exception to drop me into the debugger.
17:35:35 bauzas mriedem: you won't convince me :p
17:35:42 mriedem btw, just let me say, i'm a professional engineer
17:36:00 bauzas LOL
17:36:56 bauzas I even use Atom
17:36:58 mriedem so, are https://review.openstack.org/#/c/427782/ and https://review.openstack.org/#/c/427775/ coexisting? or does the first supersede the second?
17:37:22 melwitt I use pdb occasionally
17:37:36 dansmith mriedem: they can co-exist.. my preference is this:
17:37:36 bauzas mriedem: I don't really like https://review.openstack.org/#/c/427775/1/nova/conductor/manager.py
17:37:56 dansmith mriedem: poke mine a bit and see if we hit the bug with it. If not, I'd like to merge it and get data before we merge yours
17:38:17 bauzas yeah, I think dansmith's change could help us getting a better situation
17:38:18 dansmith mriedem: yours doesn't hurt anything other than performance and maybe making the race harder to catch if it's still there, so I just wanted to delay
17:38:26 dansmith mriedem: but, we're also up against the deadline, so..
17:38:36 mriedem -W for now
17:41:17 cdent bbl
17:52:26 openstackgerrit Oliver Walsh proposed openstack/nova: DNM - TripleO CI test https://review.openstack.org/427536
17:59:15 dims_ mriedem : melwitt : dansmith : ServersNegativeTestJSON failed in the gate about 8-10 at least for the past 4 hours. looks like we are waiting on https://review.openstack.org/#/c/427775
17:59:39 dims_ ah which transitively is waiting on https://review.openstack.org/#/c/427782/
17:59:40 dansmith dims_: we've been working on it all morning
17:59:50 dims_ ack dansmith
18:00:21 dims_ just reporting back from watching the CI that's all :)
18:01:28 mriedem you're gonna get stabbed dims
18:01:47 mriedem lots of trolls in this cave right now :)
18:01:48 dims_ LOL
18:02:03 mriedem ok got this return/continue test finally passing
18:02:04 mriedem woot
18:02:22 melwitt dims_: yeah, it turns out https://review.openstack.org/#/c/427782 might supersede the other patch
18:03:14 dims_ thanks melwitt
18:05:57 openstackgerrit Matt Riedemann proposed openstack/nova: Continue processing build requests even if one is gone already https://review.openstack.org/427839
18:05:58 mriedem melwitt: dansmith: bauzas: dtp: ^
18:06:34 dtp k
18:37:25 openstackgerrit Dan Smith proposed openstack/nova: Allow scheduler to run cell host discovery periodically https://review.openstack.org/426826
18:37:51 dansmith sfinucan: mriedem: ^^ 0 means "default" which means "every minute" which means "meltdown"
18:38:12 dansmith also, I added run_immediately, which will mean the scheduler will do this on startup and make this more useful for things like devstack
18:38:49 sfinucan dansmith: Oh, damn. I should have remembered that 🙈
18:39:05 dansmith me too :/
18:39:30 sfinucan Good catch, nonetheless
18:39:35 mriedem yar https://github.com/openstack/oslo.service/blob/master/oslo_service/periodic_task.py#L108
18:39:44 mriedem https://github.com/openstack/oslo.service/blob/master/oslo_service/periodic_task.py#L122
18:40:41 dansmith yeah
18:41:06 mriedem i think the last time i had to deal with the innards of the periodic task code was in ATL at the juno summit
18:41:21 dansmith mriedem: but, setting it =3600 will mean it runs once an hour, but at scheduler startup which will be useful for ironic people
18:41:29 mriedem i specifically remember myself and dims whispering in the back of someone's session about it
18:41:57 mriedem whispering, maybe some giggling
18:42:17 mriedem yeah on startup seems ok
18:45:23 mriedem ha

Earlier   Later