Earlier  
Posted Nick Remark
#openstack-nova - 2017-01-27
23:08:09 superdan which I see I have tabs in.. gdi
23:17:56 mriedem ok the 55_placement thing looks good now
23:19:18 mriedem now we play the waiting game
23:21:29 superdan cool
23:21:34 superdan personally,
23:21:38 superdan I hate the effing waiting game
23:21:45 superdan I've been playing it all week and I'm done with it
23:40:59 openstackgerrit Pushkar Umaranikar proposed openstack/nova: Adopts keystoneauth with glance client. https://review.openstack.org/412634
23:42:19 openstackgerrit Pushkar Umaranikar proposed openstack/nova: Adopts keystoneauth with glance client. https://review.openstack.org/412634
23:48:16 mriedem diana_clarke: just went through https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:man - some comments inline,
23:48:21 mriedem i think there are only a few that need some tweaks
23:48:44 mriedem like discover_hosts should come after create_cell because you can't map the hosts to a cell w/o a cell
23:50:45 openstackgerrit Matt Riedemann proposed openstack/nova: DNM: hack ironic with resource providers https://review.openstack.org/426296
23:52:53 diana_clarke mriedem: Yes, thanks a ton! I'll circle back and add more detail etc monday at the latest.
23:53:32 mriedem superdan: passed http://logs.openstack.org/61/417961/40/check/gate-grenade-dsvm-neutron-multinode-ubuntu-xenial/5fb6f74/
23:53:58 superdan like, yay
23:54:21 mriedem http://logs.openstack.org/61/417961/40/check/gate-grenade-dsvm-neutron-multinode-ubuntu-xenial/5fb6f74/logs/new/screen-n-sch.txt.gz#_2017-01-27_23_44_07_736
23:54:30 mriedem 2017-01-27 23:44:07.736 12381 DEBUG nova.scheduler.filter_scheduler [req-f76d4b01-c248-4de4-8675-a4cd3cb6d4cb tempest-AttachInterfacesTestJSON-881960388 tempest-AttachInterfacesTestJSON-881960388] Skipping call to placement, as upgrade in progress. _get_all_host_states /opt/stack/new/nova/nova/scheduler/filter_scheduler.py:179
23:54:37 superdan woot
23:55:45 mriedem wonder what the whiny ass grenade + live migration job is complaining about
23:56:44 mriedem heh wtf http://logs.openstack.org/61/417961/40/check/gate-grenade-dsvm-neutron-multinode-live-migration-nv/8c363cd/logs/devstack-gate-post_test_hook.txt.gz
23:57:02 mriedem tdurakov: ^
23:57:08 mriedem grenade + live migration apparently never passes
23:57:17 superdan lol
23:57:29 mriedem http://logs.openstack.org/61/417961/40/check/gate-grenade-dsvm-neutron-multinode-live-migration-nv/8c363cd/logs/new/tempest_conf.txt.gz
23:57:39 mriedem block_migration_for_live_migration = False live_migration = False
23:58:50 melwitt I've noticed that before. when all tests are skipped, it doesn't consider that a success
#openstack-nova - 2017-01-28
00:00:45 mriedem something changed on 1/21
00:08:07 mriedem single-node grenade failed http://logs.openstack.org/61/417961/40/check/gate-grenade-dsvm-neutron-ubuntu-xenial/e16142b/
00:09:57 mriedem looks like placement didn't get installed http://logs.openstack.org/61/417961/40/check/gate-grenade-dsvm-neutron-ubuntu-xenial/e16142b/logs/new/screen-n-cpu.txt.gz?level=TRACE
00:10:00 mriedem or upgraded
00:10:28 mriedem http://logs.openstack.org/61/417961/40/check/gate-grenade-dsvm-neutron-ubuntu-xenial/e16142b/logs/new/screen-n-sch.txt.gz?level=TRACE
00:12:19 mriedem hmmm
00:12:35 mriedem superdan: in grenade, when we install placement, are we installing the newton version or ocata version?
00:13:43 superdan mriedem: well.....
00:13:50 superdan mriedem: I dunno when the git tree gets updated, let me look
00:14:03 superdan you think we're starting an old placement service which only single node grenade cares about?
00:14:07 superdan that's...a good point
00:15:10 tdurakov mriedem: double wtf http://logs.openstack.org/61/417961/40/check/gate-grenade-dsvm-neutron-multinode-live-migration-nv/8c363cd/console.html#_2017-01-27_23_16_09_271784
00:15:39 mriedem superdan: i think we're installing old placement in any grenade scenario,
00:15:53 superdan multinode doesn't care though
00:15:54 mriedem it's just that we don't fail in the multinode grenade job b/c the scheduler doesn't use placement b/c of the newton compute
00:15:56 mriedem right
00:15:59 mriedem single-node cares, and dies
00:16:04 superdan hmm
00:16:05 mriedem b/c the scheduler needs ocata placement
00:16:14 superdan I don't know where we actually update the git tree though
00:16:19 superdan but I can totally believe that
00:16:50 mriedem yeah i don't see where the stack happens on the target side
00:16:58 superdan we don't stack
00:17:09 superdan I should have fought harder to merge the shit we had working this morning
00:17:39 superdan perfect timing for sdague to leave
00:18:18 mriedem did that work with single-node grenade?
00:18:49 superdan yeah,
00:18:55 superdan because we did it inside the nova service
00:19:00 superdan stack_install_service nova
00:19:03 superdan is where it is upgraded I bet
00:19:07 mriedem oh,
00:19:10 mriedem YEAH
00:19:11 mriedem mfer
00:19:13 superdan which we have not done in 55_placement of course
00:19:15 mriedem so 55_placement again
00:19:19 superdan le sigh
00:19:19 mriedem bites our arseholes
00:19:23 mriedem la creme
00:19:26 superdan right, that's my point above about not fighting harder
00:19:37 mriedem fuck a duck
00:19:40 superdan yeah
00:19:42 mriedem so do we make it 65_placement?
00:19:45 superdan no,
00:19:51 superdan because then computes will not start in 60_nova
00:19:52 mriedem although nova depends on placement
00:19:53 superdan they will bail
00:19:55 mriedem yeah
00:19:56 mriedem fuck
00:20:05 mriedem so....
00:20:06 ptcBRO Hey guys, I have instances with invalid data in the instance.info_cache. Is there a recommended way to invalidate this cache?
00:20:11 superdan I think we have to revert to before this change, minus the inflamatory correctness checking I had in there
00:20:21 mriedem superdan: couldn't we install nova from 55_placement?
00:20:27 mriedem i asked about that in your change actually
00:20:40 mriedem re-installing it from 60_nova is just redundant
00:20:42 mriedem but who cares
00:20:48 superdan mriedem: no
00:20:57 superdan mriedem: because it will install new nova before we have a chance to do things like from-newton and stuff
00:21:15 superdan and within-newton, more specifically
00:21:44 mriedem ok i'll just trust you
00:21:53 superdan surely you don't think that's legit anyway right?
00:21:57 mriedem you're the 2nd most knowledgeable grenadier in openstack now :)
00:22:04 superdan it would be like newton upgrading nova because whatever..
00:22:15 superdan if it's a separate service, it needs to be self-contained, right?
00:22:22 mriedem yar
00:23:40 mriedem cool, well, at least i feel like we're getting closer
00:23:49 mriedem and by we, i mean you
00:23:50 mriedem :)
00:23:54 superdan really? because now we're where we were 24 hours ago
00:24:06 superdan I'm not at all impressed
00:24:24 mriedem superdan: need to call out anything in the commit message about why it has to be this way for when sdague asks?
00:24:49 superdan I was just going to do a comment on it, but I can I guess
00:25:09 superdan I just want to merge this shit and have a weekend, I'm becoming less interested in the minutia
00:25:11 mriedem either/or, i left a comment too

Earlier   Later