Earlier  
Posted Nick Remark
#openstack-nova - 2017-02-02
20:37:59 mriedem i said we can start running it in one gating job for nova in pike as a start
20:38:01 EmilienM in https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html#completion-criteria
20:38:09 mriedem because we have a unicorn snowflake job for stuff like that already
20:38:11 EmilienM mriedem: 2 goals
20:39:05 mriedem ok, so i guess it's a goal for us then anyway
20:39:10 mriedem i'll throw it in our ptg etherpad
20:40:53 dims_ dansmith : i don't think the fuel team ever picked it up from where we left off here in nova. so probably not very many (http://git.openstack.org/cgit/openstack/fuel-library/tree/deployment/puppet/openstack_tasks/manifests/openstack_controller/openstack_controller.pp)
20:41:12 dims_ jaypipes : amirite?
20:41:35 dansmith dims_: gotcha
20:42:14 EmilienM mriedem: I will propose to run tripleo job in the gate for nova
20:42:21 mriedem EmilienM: i will -1
20:42:25 EmilienM of course you will
20:42:30 EmilienM but you'll have to explain why
20:42:45 mriedem because it's not even non-voting in the nova check queue for starters
20:42:50 mriedem we aren't going to gate on something right off the bat
20:43:00 EmilienM ok, let's make non voting first
20:43:06 EmilienM and see how it goes
20:43:07 mriedem are you talking 1 job or 6?
20:43:14 EmilienM but we need to stop ignoring the world outside devstack
20:43:19 EmilienM 1 job
20:43:23 EmilienM which takes 50 min max
20:43:30 mriedem wfm
20:43:35 EmilienM cool
20:43:56 openstackgerrit Dan Smith proposed openstack/nova master: Don't ever cache service versions at zero https://review.openstack.org/428404
20:43:56 openstackgerrit Dan Smith proposed openstack/nova master: Work around deployments with unsupported API services https://review.openstack.org/428415
20:44:16 dansmith mriedem: ^ untested, but might workaround the issue for experimental and unsupported setups
20:44:21 mriedem yup
20:48:31 openstackgerrit Dan Smith proposed openstack/nova master: Don't ever cache service versions at zero https://review.openstack.org/428404
20:48:32 openstackgerrit Dan Smith proposed openstack/nova master: Clarify the language in the apache wsgi sample https://review.openstack.org/428417
20:48:37 dansmith mriedem: also recommend this, since there's clearly confusion around the word "experimental"
20:49:19 dansmith and with that, I'm going to walk away for a bit.
20:49:51 mriedem jaypipes: https://review.openstack.org/#/c/428375/
20:49:59 EmilienM mriedem: the tripleo job has finished to run, http://logs.openstack.org/60/428360/2/experimental/gate-tripleo-ci-centos-7-nonha-multinode/6ca334c/logs/subnode-2/var/log/nova/nova-compute.txt.gz
20:50:07 EmilienM mriedem: let me know if logs are not enough I can increase it
20:50:49 EmilienM mriedem: the error is here: http://logs.openstack.org/60/428360/2/experimental/gate-tripleo-ci-centos-7-nonha-multinode/6ca334c/logs/subnode-2/var/log/nova/nova-api.txt.gz#_2017-02-02_20_42_17_097
20:51:17 mriedem wish i could filter these logs based on level
20:51:45 mriedem i expected to see different errors there
20:51:48 mriedem like real ERROR level issues
20:51:54 edleafe cdent: what about just changing objects.Allocation.used to a NonNegativeIntegerield?
20:52:24 cdent edleafe: I thought we established those didn't exist?
20:52:52 cdent edleafe: and also, in the past, even if we did have that we still wanted the trap at the schema level
20:53:17 edleafe cdent: doh!
20:53:24 edleafe NonNegative allows zero
21:00:30 mriedem bauzas: if you're still around https://review.openstack.org/#/c/428352/
21:00:47 bauzas mriedem: I'm just writing a comment :)
21:00:52 mriedem great
21:00:52 bauzas mriedem: there is a py3 issue
21:01:05 bauzas but I'm verifying it
21:01:09 mriedem wouldn't the py3 job fail on that?
21:01:13 bauzas not sure
21:01:18 mriedem it's voting
21:01:19 bauzas mriedem: do we have meeting ?
21:01:22 edleafe meeting today?
21:01:23 mriedem crap
21:01:23 mriedem yes
21:01:31 edleafe bauzas: jinx
21:01:52 mriedem short one
21:04:17 bauzas mriedem: nevermind my comment on py3
21:10:11 tonyb mriedem: I get the quote I'm just not sure how to interpret it in the context of this discussion
21:11:11 mriedem tonyb: that the reqs team can wait :)
21:11:21 mriedem and enjoy some cake while they are waiting
21:11:26 tonyb mriedem: :)
21:11:33 tonyb the cake is a lie!
21:12:04 mriedem unless it's mikal's birthday
21:17:07 pshedimb If anyone has idea about multi node devstack (latest version) setup
21:17:26 pshedimb My comupte node is generating this error when creating an instance
21:17:29 pshedimb ERROR nova.compute.manager [req-392e02de-349a-4791-b390-4449ff466427 None None] No compute node record for host fmwpaxeon39
21:17:48 pshedimb Intially I had placement config error
21:18:05 pshedimb I copied placement config from controller to compute node
21:18:16 pshedimb And now I'm having this error
21:22:15 diana_clarke pshedimb: is placement-api in your ENABLED_SERVICES?
21:23:35 dansmith that error isn't related to placement
21:23:44 dansmith and it's not an error if it's followed by "created a service record..."
21:25:23 pshedimb dansmith, On controller placement-api is enabled
21:25:49 pshedimb On compute node, I copied placement-api related conf to nova.conf manually
21:26:57 mriedem bauzas: thanks for https://review.openstack.org/#/c/428352/
21:27:13 diana_clarke dansmith: oh, I just recall that being one of the answers to the same question here: http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2017-02-01.log.html#t2017-02-01T13:08:33
21:27:14 pshedimb dansmith, It is not followed by " "created a service record..."
21:27:17 mriedem bauzas: if you still have some stomach left, https://review.openstack.org/#/c/427499/
21:27:37 diana_clarke nevermind
21:27:37 dansmith diana_clarke: the compute node record is service and old-school RT related
21:28:00 bauzas mriedem: I had an open question on https://review.openstack.org/#/c/428352/ about older allocation records
21:28:10 bauzas mriedem: I'm not sure we auto-heal previous records
21:28:17 mriedem bauzas: probably a question for jaypipes
21:28:20 mriedem or cdent
21:28:23 bauzas yup
21:28:26 bauzas folks ?
21:29:11 bauzas mriedem: dansmith: oh man, totally forgot to amend the nova-status check for filters
21:29:13 mriedem i've got to run for awhile
21:29:20 mriedem bauzas: that's not stopship imo
21:29:24 mriedem and we could backport if needed
21:29:37 bauzas mriedem: okay, go to your meeting
21:29:55 cdent bauzas: we check allocations every periodic job in the resource tracker. if what's on the server is different from what we have now, we rewrite it
21:30:15 bauzas cdent: that's what I thought but I wanted to be sure
21:30:46 cdent bauzas: you want me to leave that response on the review too, or okay?
21:30:49 bauzas cdent: so the patch above will autofix allocations after the 60-sec default period, cool
21:30:53 cdent yes
21:31:00 bauzas cdent: nope, not needed, I +Wd it
21:31:06 cdent great
22:04:13 openstackgerrit Jiri Suchomel proposed openstack/nova master: Retry few times when creating the initial connection to libvirtd. https://review.openstack.org/416928

Earlier   Later