Earlier  
Posted Nick Remark
#openstack-nova - 2017-04-24
19:05:37 cdent is that inside our outside the virtual host?
19:05:43 cdent s/our/or/
19:05:45 smcginnis Inside.
19:06:02 cdent try moving it outside
19:06:32 cdent I seem to recall that being one of several fixes (there's been a slew of bugs and changes related to this and I don't think the actually released package has caught up)
19:06:55 mriedem https://docs.openstack.org/ocata/install-guide-ubuntu/nova-controller-install.html doesn't mention anything about known issues
19:07:09 mriedem or apache config at all, i guess because the install guide relies on the packages being ok
19:07:27 cdent mriedem: exactly, there's been some gaps
19:08:13 smcginnis Here's the full current Apache config that the package includes if you're interested: http://paste.openstack.org/show/607726/
19:08:52 cdent yeah, other than the directory clause needing to be top level that looks okay
19:09:40 mriedem i only see 2 reported bugs for placement in the nova ubuntu packges on LP
19:09:47 openstack Launchpad bug 1671509 in Ubuntu Cloud Archive "placement api configuration in apache configure CustomLog incorrectly" [High,Fix committed] - Assigned to Corey Bryant (corey.bryant)
19:09:47 mriedem https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1671509
19:09:53 mriedem https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1674465
19:09:54 openstack Launchpad bug 1674465 in nova (Ubuntu) "wsgi scripts shouldn't grant on /usr/bin" [Undecided,Confirmed]
19:10:09 mriedem neither of those sound like what you're hitting
19:11:10 cdent strange I swear I had talked to corey about this, but I suppose it could have been one of the rdo people as they have had similar problems
19:11:12 smcginnis Nope, still getting 404's after moving the Directory piece out of the VirtualServer.
19:11:25 mriedem smcginnis: did you restart it?
19:11:30 smcginnis s/VirtualServer/VirtualHost/
19:11:40 smcginnis yeah, restarted apache, then tried restarting the host.
19:14:05 cdent smcginnis: what's your curl?
19:15:48 smcginnis curl -s -H "X-Auth-Token: $OS_TOKEN" http://192.168.1.230:8778/placement
19:16:02 cdent smcginnis: oh, yeah, drop the 'placement'
19:16:08 cdent when it is on a port, there's no prefix
19:16:26 cdent or change the WSGIScriptAlias from / to /placement
19:16:37 smcginnis Shernuf: {"versions": [{"min_version": "1.0", "max_version": "1.4", "id": "v1.0"}]}
19:17:14 cdent there's a docs bug which discusses that the service catalog entry is wrong when on a port
19:17:15 smcginnis cdent: So if I just change my catalog endpoint to not include /placement, are there going to be an issues with code expecting that in the path?
19:17:17 cdent lemme see if I can find that
19:17:43 mriedem smcginnis: we don't put that in code anywhere
19:17:43 cdent the code always uses the service catalog, so should be no problems
19:17:47 mriedem right
19:17:57 smcginnis Good, that's what I was hoping.
19:18:19 mriedem gah
19:18:20 mriedem url | http://controller/placement
19:18:27 mriedem ^ is in the install guide
19:18:33 mriedem cdent: is that what you're referring to?
19:18:33 cdent smcginnis mriedem https://bugs.launchpad.net/openstack-manuals/+bug/1683585
19:18:33 openstack Launchpad bug 1683585 in openstack-manuals "Placement endpoint configuration incorrect as written" [High,Confirmed] - Assigned to Brian Moss (bmoss)
19:18:34 smcginnis mriedem: yep
19:19:04 smcginnis Or Ubuntu shouldn't be putting it on a different port.
19:19:35 cdent there's a lot of confusion on how to manage the wsgi-based stuff under apache
19:19:57 cdent which I (incorrectly) had assumed was a known thing
19:20:31 mriedem coreycb: are you still with canonical?
19:21:09 coreycb mriedem, hey, yes
19:21:23 mriedem ?
19:21:23 openstack Launchpad bug 1683585 in openstack-manuals "Placement endpoint configuration incorrect as written" [High,Confirmed] - Assigned to Brian Moss (bmoss)
19:21:23 mriedem coreycb: can you comment on the state of the nova-placement-api package wrt https://bugs.launchpad.net/openstack-manuals/+bug/1683585 /
19:21:52 coreycb mriedem, sure, taking a look
19:22:13 mriedem smcginnis: sounds like you should be able to do the workaround in that bug report by deleting your endpoints and recreating them with the 8778 port
19:22:31 smcginnis mriedem: Just finished recreating them, let's see how this goes.
19:24:20 coreycb smcginnis, i've always created them with the port numbers, i need to what chris was talking about
19:24:33 coreycb that is, i need to look into
19:25:18 cdent coreycb: I think the fundamental issue was that I said (in a review of the install guide): in the long term we want to use prefixes like /placement instead of ports
19:25:24 cdent but that got translated into changing the docs
19:25:34 smcginnis coreycb: Great. Yeah, I was just following the docs.o.o ubuntu instructions, and that doesn't work right now.
19:25:35 cdent causing a mismatch with the packges
19:26:00 smcginnis Hmm, not I see this in the scheduler log: The placement API endpoint not found. Placement is optional in Newton, but required in Ocata. Please enable the placement service before upgrading.
19:26:36 mriedem smcginnis: you're getting an endpoint not found error from ksa now
19:26:57 mriedem smcginnis: the service type and endpoint name are 'placement' right?
19:27:09 coreycb cdent, yep
19:27:54 mriedem cdent: unless the ubuntu packages are going to change to take the port number out of the apache config it seems we should get the install guide updated to create the endpoint with the port number
19:28:05 cdent mriedem: yes
19:28:13 coreycb mriedem, cdent: yes agreed
19:28:23 cdent that's pretty much where asettle and I landed when talking about it last week
19:28:28 mriedem if canonical changed the apache config in a new package release, that would be confusing (at least for ocata)
19:28:49 mriedem you could probably mirate the config somehow at install/update time for the new package, but...
19:28:52 mriedem *migrate
19:28:59 smcginnis Well, if our long term goal is to get rid of ports, shouldn't we make sure new services aren't getting set up that way by default?
19:29:34 mriedem smcginnis: sure, but then canonical has to change the config in their package and provide a migration i'd think
19:29:42 mriedem which is probably a PITA after ocata GA'ed
19:29:57 coreycb mriedem, smcginnis: yeah we'd definitely want to do that on a release boundary if we did
19:32:23 smcginnis mriedem: OK, instance still failing because it's filtering out all my one hosts. I should be able to figure it out from here though. Placement seems to be sorted.
19:32:40 smcginnis mriedem, cdent, coreycb: Thanks for the help.
19:32:45 coreycb smcginnis, maybe cells v2 is needed next
19:33:08 smcginnis coreycb: Any docs.o.o instruction issues with that? I followed the docs on that one too.
19:33:40 coreycb smcginnis, not that i know of
19:34:10 smcginnis coreycb: OK, I'll let you know if I find otherwise.
19:34:13 mriedem yes
19:34:19 mriedem it's in the compute install guide
19:34:19 coreycb smcginnis, ok thanks
19:34:23 mriedem you have to discover the host
19:34:32 mriedem smcginnis: https://docs.openstack.org/ocata/install-guide-ubuntu/nova-compute-install.html
19:34:37 smcginnis mriedem: Yep, did that.
19:34:44 mriedem coreycb: if you can comment in that bug i can move forward with updating the install guide
19:34:48 smcginnis mriedem: Unless that needs to be done again since placement was hosed?
19:34:51 mriedem basically, we create the placement endpoint in keystone with ports for ocata
19:35:01 mriedem and we could reconsider package changes for the apache config in pike
19:35:23 mriedem smcginnis: is the nova-compute log showing that it's creating the resource provider in placement now?
19:36:03 smcginnis mriedem: Created resource provider record via placement API for resource provider with UUID
19:36:11 mriedem ok nice
19:36:34 mriedem smcginnis: are you using a flavor that's too big or something?
19:36:37 mriedem for your compute node?
19:36:53 coreycb mriedem, done
19:36:59 mriedem coreycb: thanks
19:37:04 smcginnis mriedem: Nope, tiniest one. Enabled debug now, so I can see what's going on with the filtering.
19:38:08 smcginnis mriedem: Well, whatever it was, restarting to enable debug seems to have fixed the issue. Got an ACTIVE running instance.
19:38:28 smcginnis mriedem: I'll go back in my own corner now. Thanks!
19:38:51 mriedem hmm

Earlier   Later