Earlier  
Posted Nick Remark
#openstack-nova - 2017-04-24
18:14:51 openstackgerrit Matt Riedemann proposed openstack/nova master: libvirt: remove redundant and broken iscsi volume test https://review.openstack.org/459420
18:14:53 mriedem ^ fixes cuhler's issue pointed out earlier, and unblocks us from using brick 1.12.0
18:15:32 smcginnis Following the docs.o.o install instructions for Ubuntu. Getting this error :The requested URL /placement/resource_providers was not found on this server"
18:15:35 smcginnis Any pointers?
18:16:02 mriedem smcginnis: hello new user, please see the channel topic and gtfo
18:16:09 mriedem :)
18:16:23 mriedem smcginnis: where are you getting the error? which service?
18:16:29 smcginnis mriedem: Just remember that when you want us to adopt placement usage too. :P
18:16:51 smcginnis mriedem: In the nova-compute log when trying to create a first test instance.
18:17:07 smcginnis Actually, regular intervals it looks like.
18:17:10 mriedem if compute couldn't talk to placement it shouldn't have started up in the first place
18:17:15 mriedem yeah, it should be spewing errors
18:17:28 mriedem are you able to make curl requests to placement from your compute node?
18:17:33 smcginnis From this: Failed to create resource provider record in placement API
18:17:59 mriedem smcginnis: source the same credentials that are in nova.conf on your compute host, and then create a token for those creds and try a curl request to the same placement endpoint url in the service catalog
18:18:12 mriedem to see if it's compute misconfig or something else
18:18:27 mriedem also, is the placement service logging anything?
18:18:30 mriedem it runs under apache
18:18:45 smcginnis Where does that go?
18:19:08 mriedem /var/log/httpd? i think it has to be configured
18:19:15 mriedem devstack puts it into it's own log file
18:19:23 smcginnis Ah, /var/log/apache/nova_placement*
18:19:49 smcginnis Hmm, "nova" placement. Yeah, good luck getting me to use this.
18:19:52 smcginnis jk
18:19:57 mriedem https://github.com/openstack-dev/devstack/blob/master/lib/placement#L168
18:20:20 mriedem yeah, i think the ubuntu packagers were throwing nova in the name since that's where the code is sourced from
18:20:29 mriedem which is going to be a fun packaging rename later
18:20:41 smcginnis mriedem: Actual deployment looks like it puts them in nova_placement_error.log and nova_placement_access.log on Ubuntu.
18:21:00 smcginnis Nothing in either file though.
18:21:07 mriedem is it running?
18:22:10 smcginnis mriedem: Nope. Looks like the packages must not configure Apache correctly.
18:22:13 smcginnis mriedem: Loaded: not-found (Reason: No such file or directory)
18:22:25 smcginnis OK, go the clue I needed. I'll dig from here.
18:22:31 smcginnis Taking it this is not a known issue though.
18:22:32 mriedem i had heard of people complaining that the ubuntu packages were messed up
18:22:45 mriedem at least while they were working on the docs,
18:22:57 mriedem if there was a known issue, i'd think it would have been capture in the install guide though, but i've been out of the loop there
18:23:02 mriedem cdent might know but he's gone
18:23:21 smcginnis mriedem: If I find anything I'll try to update the docs. Thanks.
18:23:25 smcginnis :q
18:30:23 mriedem sdague: can we get this into stable/ocata to unblock the LM job there? https://review.openstack.org/#/c/458843/
18:35:27 openstackgerrit Dan Smith proposed openstack/nova master: WIP: De-complicate some of the instance delete path https://review.openstack.org/458636
18:35:27 openstackgerrit Dan Smith proposed openstack/nova master: Make server groups api aware of multiple cells for membership https://review.openstack.org/457338
18:35:28 openstackgerrit Dan Smith proposed openstack/nova master: WIP: Move to proper target_cell calling convention https://review.openstack.org/458634
18:35:28 openstackgerrit Dan Smith proposed openstack/nova master: Make target_cell() yield a new context https://review.openstack.org/458635
18:35:29 openstackgerrit Dan Smith proposed openstack/nova master: Sort CellMappingList.get_all() for safety https://review.openstack.org/443174
18:35:29 openstackgerrit Dan Smith proposed openstack/nova master: Clean up ClientRouter debt https://review.openstack.org/444487
18:35:30 openstackgerrit Dan Smith proposed openstack/nova master: DNM: Canary test against multi-cell devstack https://review.openstack.org/458537
18:35:36 openstackgerrit Dan Smith proposed openstack/nova master: Add workaround to disable group policy check upcall https://review.openstack.org/442736
18:43:41 smcginnis mriedem: FYI, Ubuntu packages put the placement stuff under port 8778.
18:44:01 smcginnis mriedem: I seem to have that resolved now, but it's failing to find resource types when updating, etc.
18:44:23 smcginnis mriedem: Is there an installation step that needs to be run again to get resource info populated in placement?
18:44:45 mriedem resource types?
18:44:52 mriedem got an error message?
18:44:54 mriedem or log
18:45:04 smcginnis Failed to retrieve filtered list of resource providers from placement API for filters
18:45:09 smcginnis Resource could not be found.
18:45:43 dansmith mriedem: <3
18:45:59 mriedem dansmith: that's my way of paying you back for bugging you all morning
18:46:09 dansmith heh
18:46:45 mriedem smcginnis: hmm, you might not have the resource classes, or any resource providers, loaded into placement
18:46:49 mriedem resource provider == compute node
18:47:04 mriedem smcginnis: so now that placement is working, are you seeing things populating it in the nova-compute logs?
18:47:23 mriedem smcginnis: the update_available_resource periodic task in the compute service will update placement
18:47:27 mriedem every 1 min
18:47:37 smcginnis Failed to create resource provider record in placement API for UUID e3c2178a-8fc6-47d7-9ee1-c01a067213aa. Got 404: 404 Not Found
18:48:44 mriedem hmm wtf
18:49:02 mriedem smcginnis: nothing in the placement logs?
18:50:08 smcginnis mriedem: Just a bunch of 404s.
18:50:19 mriedem i don't see where we'd ever return a 404 when trying to POST /resource_providers
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?

Earlier   Later