Earlier  
Posted Nick Remark
#openstack-nova - 2017-01-25
21:09:32 bauzas but http://logs.openstack.org/30/424730/6/check/gate-grenade-dsvm-neutron-ubuntu-xenial/16175d7/logs/new/screen-n-cpu.txt.gz#_2017-01-25_20_43_30_774
21:10:04 bauzas and cdent bailed out
21:10:13 bauzas :(
21:11:14 bauzas the creds look correct to me also
21:14:31 bauzas dansmith: okay, so when comparing a tempest nova.conf and a grenade nova.conf, both are similar
21:14:54 bauzas I guess the problem is that we don't correctly have the placement API running
21:29:47 mriedem dansmith: how goes it today?
21:30:09 dansmith mriedem: lots of gate failures and still some discussion over the mysql host change
21:31:08 dansmith mriedem: and sounds like bauzas is still struggling with the grenade change
21:31:34 bauzas indeed
21:31:38 mriedem this https://review.openstack.org/421399 ?
21:31:43 mriedem re: mysql host
21:31:45 bauzas the gate is also 4 hours off
21:32:11 dansmith yeah
21:32:12 mriedem dansmith: we can maybe just drop https://review.openstack.org/421399
21:32:16 bauzas so, today is probably our last chance to get things done
21:32:31 dansmith mriedem: we can't because we're discovering from the subnode in the devstack multinode job right?
21:32:33 dansmith see my comment just now
21:32:35 bauzas andreykurilin: around ?
21:32:50 andreykurilin bauzas: yes
21:32:51 mriedem i couldn't remember if i needed https://review.openstack.org/421399 for how i was previously doing things in devstack
21:33:01 bauzas andreykurilin: where are we wiht all the client changes ?
21:33:18 bauzas missed a bit of scope since I'm working on another thing
21:33:44 dansmith mriedem: I'm not even sure what variable d-g has that address in
21:34:38 andreykurilin bauzas: all client changes?
21:34:52 bauzas andreykurilin: the fixes for 7.1.0
21:35:09 bauzas for *releasing
21:35:20 mriedem dansmith: "Because we're calling discover_hosts from the subnode in devstack-gate" isn't actually true
21:35:21 andreykurilin bauzas: it is the last one - https://review.openstack.org/#/c/424256/
21:35:29 dansmith mriedem: eh?
21:35:38 mriedem we call it from the primary node in d-g
21:36:08 mriedem dansmith: i'm thinking i needed the mysql host fix for something to do with https://review.openstack.org/420976
21:36:13 mriedem but need to remember quick
21:36:24 dansmith mriedem: isn't this using ansible to run it on the subnode? https://review.openstack.org/#/c/424252/4/devstack-vm-gate.sh@239
21:36:48 mriedem dansmith: no,
21:36:49 mriedem $ANSIBLE primary
21:36:52 mriedem == primary node
21:37:12 dansmith why via ansible then?
21:37:52 mriedem because that's what runs random shell stuff on the node?
21:37:56 mriedem and what i was told to use
21:38:08 dansmith mriedem: okay
21:38:23 dansmith mriedem: I just removed it, so we'll see
21:39:14 openstackgerrit Dan Smith proposed openstack/nova: WIP: Collected release notes for Ocata CellsV2 https://review.openstack.org/424737
21:39:15 openstackgerrit Dan Smith proposed openstack/nova: Move instance creation to conductor https://review.openstack.org/319379
21:39:42 mriedem dansmith: so i just abandoned https://review.openstack.org/#/c/421399/
21:40:04 mriedem ok you broke the connection to it as a dep, good
21:40:13 dansmith yeah
21:41:10 dansmith I still think the assertion that the subnode shouldn't know the database host is based on nova-centric architecture, but happy to have one fewer thing in the dep chain
21:41:23 mriedem yeah basically f it and we'll sort it out later :)
21:41:35 dansmith yep
21:43:47 mriedem so the devstack change for discover_hosts should be approved at some point today too, just pinged dtroyer
21:44:07 dansmith I pinged him earlier
21:44:28 dansmith the --verbose one failed jenkins in the gate, but should be on its way again soon
21:44:41 dansmith check was over 300 earlier today, but looks like it has calmed down a bit, which is good
21:45:17 mriedem es muy triste
21:46:26 dansmith heh
21:47:45 dansmith melwitt: mriedem: should we remove mriedem's -2 on the bottom quotas patch since we're close? maybe let melwitt hold the -2 onit?
21:47:50 dansmith https://review.openstack.org/#/c/410945/
21:48:20 dansmith actually can we go ahead and merge the bottom two?
21:49:39 mriedem i thought we weren't going to merge those unless the counting resources one was good
21:49:44 mriedem i've removed the -2 btw
21:50:17 mriedem b/c we don't have reservations in the api db in the bottom changes i thought
21:50:26 dansmith ah
21:51:19 dansmith the counting patch is massive
21:51:24 dansmith which I guess is why it's still WIP
21:51:41 mriedem yeah, and probably too risky at this point
21:52:00 mriedem i.e. i think we need more burn in time with testing for a change like that
21:52:33 dansmith so you're calling it?
21:52:34 mriedem so does that automatically mean the bottom two changes can't get in? i believe they will just fallback to the main db for reservations/usages since those won't be in the api db
21:52:37 mriedem well,
21:52:44 mriedem seems pretty damn risky at this point
21:52:53 mriedem is melwitt around?
21:53:23 dansmith from what I saw of the first two, it doesn't really change anything so I would expect the bottom ones are okay, but.. I forgot about reservations
21:53:50 mriedem and usages
21:53:56 mriedem i think those were the 2 tables that weren't being ported
21:54:27 dansmith aye
21:54:49 dansmith well, john and I have been hitting that hard in the last day expecting to get it in, but I dunno. I guess we'll wait for melwitt to get back and advise
22:09:05 bauzas if someone could tell me how we can raise keystoneclient.Unauthorized exceptions when calling https://github.com/openstack/keystoneauth/blob/master/keystoneauth1/session.py#L616 ...
22:09:24 bauzas I'm puzzled
22:09:51 bauzas mmmmmpf nvm https://github.com/openstack/keystoneauth/blob/master/keystoneauth1/session.py#L652
22:14:39 bauzas mriedem: still around?
22:15:16 bauzas mriedem: I'd love more context about https://review.openstack.org/#/c/416810/
22:20:07 mriedem bauzas: context how?
22:20:09 mriedem did you read the bug report?
22:20:37 mriedem or the related change - nova.conf was misconfigured for how to connect to placement for awhile with keystone v3
22:20:41 mriedem so you'd get 401
22:21:11 bauzas mriedem: yup, saw the change in devstack lib/placement
22:21:33 bauzas but I'm hitting the same 401 in grenade job
22:22:19 bauzas AFAICS, the value is still "Default" https://github.com/openstack-dev/devstack/blob/7a1e6f042f00ac94ec30bb8c6bf5d05b34623832/lib/keystone#L107
22:24:21 mriedem not sure, would have to see that everything is configured the same and if not, what's different and what's missing
22:24:26 mriedem but i'm taking maya to the pool so back in a few hours
22:25:08 bauzas no worries
23:15:59 bauzas dansmith: still around?
23:16:23 bauzas dansmith: I wonder if we don't run init_placement() method within grenade
23:16:58 bauzas just verifying the grenade log, but in case you know...
23:17:00 dansmith bauzas: if you don't see it, then we don't
23:17:16 dansmith bauzas: if we don't in neutron devstack, and you don't see it in grenade then, we don't
23:17:42 bauzas sec, verifying the grenade deployment
23:18:52 bauzas dansmith: confirmed
23:19:03 bauzas dansmith: can't find it in http://logs.openstack.org/30/424730/6/check/gate-grenade-dsvm-neutron-ubuntu-xenial/16175d7/logs/grenade.sh.txt.gz

Earlier   Later