Earlier  
Posted Nick Remark
#openstack-nova - 2017-04-24
18:50:28 mriedem unless you're not making it to placement?
18:50:39 mriedem can you make a curl request against the placement endpoint in the service catalog?
18:50:57 mriedem i wonder if you're getting an endpoint not found from keystone or something
18:51:10 smcginnis I get : {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}
18:51:36 mriedem ok check your nova.conf [placement] section
18:51:42 mriedem on the compute host
18:51:58 mriedem well, you'll need a token to curl to placement
18:52:02 mriedem did you pass a token?
18:52:28 smcginnis mriedem: No, was just seeing if I could even hit it.
18:52:55 mriedem source the credentials that you have in nova.conf under the [placement] group using the normal OS_* variables
18:53:04 mriedem get a token and pass that to the curl request headers
18:54:45 smcginnis mriedem: Happen to have an example of that curl command line?
18:54:58 mriedem yeah sec
18:56:29 mriedem hmm seems the docs have changed for the api guide and now i've lost my reference
18:57:17 mriedem here we go https://developer.openstack.org/api-guide/quick-start/api-quick-start.html
18:57:43 mriedem OS_TOKEN=$(openstack token issue -c id -f value)
18:58:01 mriedem is what i use to get the token and store into a variable
18:58:27 smcginnis OK, I see X-Auth-Token...
18:58:34 mriedem curl -s -H "X-Auth-Token: $OS_TOKEN" <whatever your placement endpoint is in the service catalog>
18:59:01 mriedem "openstack catalog list" to get the service catalog
18:59:41 smcginnis mriedem: Still 404: The resource could not be found.
19:00:39 mriedem are you trying to hit it on port 8778 ?
19:01:46 smcginnis yes
19:02:32 smcginnis mriedem: I wonder if there is something else wrong with the apache config the Ubuntu package has.
19:02:37 mriedem i assume there is
19:02:47 mriedem but i'm like a baby lamb when it comes to apache config
19:03:02 mriedem but i see cdent snuck back in....
19:03:35 cdent uh oh
19:04:00 cdent that placement not found business is usually the result of a missing <Directory /path/to/the/wsgi/script> clause
19:04:03 smcginnis cdent: Do you happen to know of issues with the way Ubuntu packages set up placement?
19:04:22 smcginnis cdent: They set up a virtual host on *:8778
19:04:45 cdent yeah, that's okay as long as the service catalog is right but without the Directory clause the script is not accessible
19:04:51 cdent lemme locate something, one sec
19:05:15 smcginnis cdent: They have WSGIScriptAlias / /usr/bin/nova-placement-api
19:05:24 smcginnis cdent: Then <Directory /usr/bin>
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

Earlier   Later