Earlier  
Posted Nick Remark
#openstack-nova - 2017-03-20
18:47:53 mriedem i'm assuming because event is None
18:48:02 sdague well, are you sure?
18:48:11 mriedem although it shouldn't be
18:48:17 sdague Received unexpected event network-vif-unplugged-8ed92137-a81a-4afd-a391-854848cd2916 for instance
18:48:18 mriedem because if it was https://github.com/openstack/nova/blob/6f66119153a36ab2ee7d63c98418af3a56fd1f1e/nova/compute/manager.py#L6867
18:48:35 mriedem ah yeah
18:48:37 mriedem my mistake
18:48:45 mriedem when i originally looked at it, i thought it was using _event
18:50:01 mriedem https://github.com/openstack/oslo.concurrency/blob/master/oslo_concurrency/processutils.py#L355 ?
18:50:03 sdague and there are tons of these other places
18:50:12 mriedem https://github.com/openstack/oslo.concurrency/blob/master/oslo_concurrency/processutils.py#L385
18:50:29 sdague you think that's blowing up?
18:50:38 mriedem "Logged from file processutils.py, line 385"
18:51:33 jaypipes sean-k-mooney, sfinucan, alex_xu, edleafe, Yingxin, moshele: https://review.openstack.org/447643
18:53:47 mriedem but yeah they are everywhere https://goo.gl/sPpPN0
18:55:23 sdague mriedem: right
18:56:51 mriedem https://github.com/openstack/oslo.log/blob/master/oslo_log/formatters.py#L273
18:57:02 mriedem so what sets the log record.args?
18:57:50 sdague most of these stack traces include a daemon.py reference
18:57:56 sdague I wonder if it's this change - https://review.openstack.org/#/c/360252/
18:58:43 mriedem data['args'] = None
18:59:25 sdague so... yes, it would be that change then
18:59:38 sdague it's one that angus seems to have written over the summer, and dims just merged
19:00:23 mriedem started using that version 2 weeks ago https://review.openstack.org/#/c/442067/
19:00:23 sdague I'm going to see what a revert does there in the run
19:00:26 sdague yeh
19:00:28 dims sdague : https://review.openstack.org/#/c/447334/
19:00:57 dims does that help?
19:01:15 sdague dims: I think so
19:01:41 mriedem message:"TypeError: 'NoneType' object is not iterable" AND message:"Logged from file" AND build_change:"447334"
19:02:38 sdague mriedem: yeh, though mostly at debug, so it wouldn't always show there
19:03:04 sdague but, http://logs.openstack.org/34/447334/1/check/gate-tempest-dsvm-neutron-src-oslo.privsep-ubuntu-xenial/c147be6/logs/screen-n-cpu.txt.gz looks clean
19:06:51 openstackgerrit Eric Brown proposed openstack/python-novaclient master: Remove py34 tox env and pypi classifier https://review.openstack.org/442847
19:13:50 wally Hello, all, i got some question about the Openstack Ocata nova placement api,.
19:14:22 wally I tried installed ocata on ubuntu 1604, and also configure the nova placement api, but still not wokring,
19:14:31 wally can anyone help?
19:14:56 wally there is nothing about this on the installation doc
19:15:01 jaypipes wally: please see /topic. It may be best to send an email to the openstack@ mailing list.
19:15:17 jaypipes wally: also "but still not working" doesn't exactly provide us much information :)
19:16:02 wally on the controller node, i install the apt install nova-placement-api
19:16:40 wally and create the placement endpoint, but when i run the nova-status upgrade check
19:16:47 wally Check: Placement API | Result: Failure | Details: Placement API endpoint not found.
19:17:03 jaypipes wally: did you add the placement endpoint to the Keystone service catalog?
19:17:09 wally i followed this link https://ask.openstack.org/en/question/102256/how-to-configure-placement-service-for-compute-node-on-ocata/
19:17:33 jaypipes wally: openstack service create --name placement --description "OpenStack Placement" placement
19:17:46 wally yeah i create this as well
19:17:54 wally openstack service create --name placement --description "OpenStack Placement" placement
19:18:30 wally dont know what is wrong?
19:18:44 jaypipes wally: and you did the endpoint create steps as well?
19:19:08 wally openstack service create --name placement --description "OpenStack Placement" placement openstack endpoint create --region RegionOne placement public http://controller:8778 openstack endpoint create --region RegionOne placement admin http://controller:8778 openstack endpoint create --region RegionOne placement internal http://controller:8778
19:19:16 wally is the enpoint good?>>
19:19:29 jaypipes wally: what does `openstack endpoint list` show?
19:19:44 wally one sec
19:19:53 jaypipes wally: also, please read /topic :)
19:19:54 wally how to paste entire log
19:20:03 jaypipes do not paste entire log.
19:20:08 jaypipes use paste.openstack.org
19:21:17 wally here is it
19:21:18 wally http://paste.openstack.org/show/603483/
19:21:32 wally @jaypipes, could you please help
19:21:58 wally i followed this doc to do https://ask.openstack.org/en/question/102256/how-to-configure-placement-service-for-compute-node-on-ocata/
19:22:33 mriedem jroll: what do people use for ironic cli? osc or ironicclient?
19:22:39 jroll mriedem: yes
19:23:01 jroll mriedem: pip install python-ironicclient gets you ironic cli and the osc plugin
19:23:17 jroll we're deprecating the former soon(TM)
19:23:25 jaypipes wally: can you hit http://10.10.10.11:8778 from your compute node?
19:23:48 wally one sec
19:23:58 mriedem jroll: ok
19:24:48 wally what do u mean hit http://10.10.10.11:8778
19:24:53 wally i can ping 10.10.10.11
19:25:48 wally in the compute node, the nova-compute.log show The placement API endpoint not found. Placement is optional in Newton, but required in Ocata. Please enable the placement service before upgrading.
19:26:46 wally and could you please check this http://paste.openstack.org/show/603484/
19:26:50 mriedem wally: hit == curl request
19:26:58 wally one sec
19:27:11 mriedem if nova.conf is cofigured properly on the compute node, but it's not trying the endpoint again, try restarting n-cpu
19:27:14 mriedem the service
19:27:37 mriedem although it should try everytime, and only log once every 10 minutes if it can't
19:28:14 mriedem also https://review.openstack.org/#/c/438328/
19:28:30 wally root@compute1:~# curl http://10.10.10.11:8778 curl: (7) Failed to connect to 10.10.10.11 port 8778: Connection refused
19:28:34 wally not working
19:28:52 mriedem see Petr's last comment in https://review.openstack.org/#/c/438328/
19:29:11 mriedem https://bugzilla.redhat.com/show_bug.cgi?id=1430540#c0
19:29:11 openstack bugzilla.redhat.com bug 1430540 in openstack-nova "[Ocata] openstack-nova-placement-api-15.0.0-1.el7.noarch missing <Directory> parameter" [Unspecified,New] - Assigned to nlevinki
19:30:12 wally so this is a bug?
19:30:24 wally but i use Ubuntu, is different with centos
19:30:44 mriedem i don't know if there are problems with the ubuntu packages
19:31:05 mriedem you could try what's specified in that bug and see if it fixes your issue
19:31:17 mriedem and if so, then yeah it's probably a packaging bug in ubuntu if you're getting the placement code from them
19:31:56 wally but anyone install the Ocata with ubuntu successfully before?
19:32:23 mriedem i'd check the comments backward from the end of that docs patch
19:32:30 mriedem where people are testing out the install guide
19:33:14 wally ...so ...
19:33:24 wally not working on Ubuntu?
19:33:41 mriedem "(2:30:44 PM) mriedem: i don't know if there are problems with the ubuntu packages"
19:33:46 openstackgerrit Roman Dobosz proposed openstack/nova-specs master: FPGA resource use cases https://review.openstack.org/318047
19:33:59 mriedem this isn't the nova ubuntu packaging channel
19:34:39 mriedem coreycb: do you do ubuntu packaging for nova stuff?
19:35:06 openstackgerrit Matt Riedemann proposed openstack/python-novaclient master: Remove deprecated baremetal CLIs and APIs https://review.openstack.org/447657
19:35:08 mriedem jroll: just for you ^
19:35:13 wally yesh i use apt install nova-placement-api

Earlier   Later