Posted	Nick	Remark
#openstack-nova - 2017-03-27
03:13:32	openstackgerrit	Maciej Szankin proposed openstack/nova-specs master: Add deprecate-nova-consoleauth spec https://review.openstack.org/450063
03:57:48	openstackgerrit	Xu Ao proposed openstack/nova master: There is a error on annotation about related options https://review.openstack.org/450071
04:30:40	openstackgerrit	Maciej Szankin proposed openstack/nova-specs master: Add deprecate-nova-consoleauth spec https://review.openstack.org/450063
04:50:47	openstackgerrit	Alex Xu proposed openstack/nova master: placement: Add Traits API to placement service https://review.openstack.org/376200
04:55:52	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Enable cold migration with target host(1/2) https://review.openstack.org/408955
05:04:56	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Refactor a test method including 3 test cases https://review.openstack.org/394738
05:05:29	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Refactor a test method including 7 test cases https://review.openstack.org/395436
05:16:54	openstackgerrit	Takashi NATSUME proposed openstack/nova master: List/show all server migration types https://review.openstack.org/430608
05:20:24	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Enable cold migration with target host(1/2) https://review.openstack.org/408955
05:20:51	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Enable cold migration with target host(2/2) https://review.openstack.org/408964
05:21:23	openstackgerrit	Takashi NATSUME proposed openstack/nova master: api-ref: Add parameters in cold migrate action https://review.openstack.org/410042
05:22:06	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Add functional tests for cold migration to same host https://review.openstack.org/414926
05:33:09	openstackgerrit	Takashi NATSUME proposed openstack/nova master: List/show all server migration types https://review.openstack.org/430608
07:49:41	openstackgerrit	jichenjc proposed openstack/nova master: WIP: add usage doc https://review.openstack.org/450105
08:33:41	openstackgerrit	Jianghua Wang proposed openstack/nova-specs master: XenAPI: support for VGPU https://review.openstack.org/450122
08:39:47	openstackgerrit	Lei Zhang proposed openstack/nova master: placement: Enable attach traits to ResourceProvider https://review.openstack.org/376201
08:39:48	openstackgerrit	Lei Zhang proposed openstack/nova master: (WIP)Add sync traits command for placement https://review.openstack.org/450125
08:41:28	openstackgerrit	Jianghua Wang proposed openstack/nova-specs master: XenAPI: support for VGPU https://review.openstack.org/450122
08:48:37	moshele	sean-k-mooney: hi
08:51:46	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Enable cold migration with target host(2/2) https://review.openstack.org/408964
08:52:20	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Add functional tests for cold migration to same host https://review.openstack.org/414926
09:08:09	gmann	alex_xu: oomichi can you check this - https://review.openstack.org/#/c/449450/
09:27:06	openstackgerrit	Ghanshyam Mann proposed openstack/nova master: Fix 'server' and 'instance' togetger in api-ref https://review.openstack.org/450141
09:31:44	openstackgerrit	Ghanshyam Mann proposed openstack/nova master: Fix 'server' and 'instance' occurrence in api-ref https://review.openstack.org/450141
09:49:14	openstackgerrit	Hironori Shiina proposed openstack/nova-specs master: Fix rendering sub-directories in README https://review.openstack.org/449000
10:01:14	alex_xu	gmann: yea, checking now
10:07:13	ygl	hi all
10:07:22	ygl	i have installed ocata on ubuntu
10:07:52	ygl	but I am unable to launch the cirros instance
10:08:02	ygl	it is saying no valid host found
10:08:08	ygl	can anyone help me please
10:09:26	ygl	the compute node is up and running
10:09:33	openstackgerrit	Alex Xu proposed openstack/nova master: placement: Enable attach traits to ResourceProvider https://review.openstack.org/376201
10:09:33	openstackgerrit	Alex Xu proposed openstack/nova master: [placement] Allow PUT and POST without bodies https://review.openstack.org/447625
10:09:34	openstackgerrit	Alex Xu proposed openstack/nova master: placement: Add Traits API to placement service https://review.openstack.org/376200
10:09:38	ygl	i see the errors in the nova-conductoer log
10:11:49	ygl	Failed to compute_task_build_instances: No valid host was found. There are not enough hosts available.
10:14:10	ygl	can anyone help me please
10:14:24	ygl	i am not able to launch the instance
10:15:46	bauwser	ygl: you should look at the scheduler logs rather
10:17:31	ygl	bauwser: i see the logs in nova-conductor
10:17:45	ygl	bauwser: no relevant logs in scheduler though
10:18:21	bauzas	ygl: the conductor is just providing you the explanation, but it's because the scheduler is returning no valid hosts
10:18:40	bauzas	ygl: so you should look at the request-id in the nova-scheduler log
10:18:50	ygl	bauzas: but i see not error in scheduler logs
10:19:08	bauzas	ygl: because it's an INFO log
10:19:30	ygl	bauzas: how should I enable debug in scheduler ?
10:19:40	bauzas	ygl: you don't need it
10:19:48	bauzas	ygl: just look at the request-id
10:20:07	bauzas	and you should find an INFO log by this request-id
10:20:32	ygl	bauzas: ok
10:22:56	ygl	bauzas: nova.filters [req-05b04f15-3076-4134-8cbf-4865b4bad754 0d0aa8e977c74babb1e1d06d4b04f2bd 4b24c5c7bed34373b38120bdcabb0432 - - -] Filter RetryFilter returned 0 hosts
10:23:01	bauzas	voila
10:23:16	bauzas	ygl: you only have one compute, right?
10:24:25	ygl	bauzas: yes
10:24:49	moshele	sfinucan: hi
10:25:02	sfinucan	moshele: howdy
10:25:06	openstackgerrit	Stephen Finucane proposed openstack/nova master: tox: Stop calling config/policy generators twice https://review.openstack.org/450153
10:25:18	bauzas	ygl: that just tells you something went bad in the compute node for the first time and when it retried the scheduler, it said "sorry, but since you tried this compute which was wrong, I don't have more computes to give you"
10:25:49	bauzas	ygl: so the problem is tied within the compute node log
10:25:51	moshele	sfinucan: can you please review my HW offload support for openvswitch patches, https://review.openstack.org/#/c/398277/ and https://review.openstack.org/#/c/398265/
10:26:51	ygl	bauzas: i see this error in compute
10:26:53	ygl	bauzas: NotFound: Basic.publish: (404) NOT_FOUND - no exchange 'scheduler_fanout' in vhost '/'
10:27:19	bauzas	ygl: is the compute running ?
10:27:49	bauzas	ygl: because the above is a rabbit error telling you that the compute can't fanout to the scheduler MQ
10:28:22	bauzas	ygl: the compute does that for telling to the scheduler(s) how many aggregates and instances it knows
10:28:48	ygl	bauzas: ok
10:28:58	ygl	bauzas: i have restarted the rabbitmq service in controller
10:29:05	ygl	bauzas: launching again to check
10:29:25	bauzas	ygl: you should rather look at why the compute rescheduled the first time the instance
10:30:03	ygl	bauzas: i didn't get u
10:30:30	bauzas	ygl: so, the boot went that way :
10:30:41	bauzas	api > conductor > scheduler > conductor > compute
10:30:51	bauzas	then the compute returned an exception
10:31:00	bauzas	so the compute rescheduled the instance, by saying
10:31:11	bauzas	compute > conductor > scheduler > conductor
10:31:27	bauzas	that's where you saw the NoValidHosts error due to the RetryFilter
10:31:37	ygl	bauzas: it again went into error state
10:31:38	bauzas	because it was rescheduling an instance request
10:31:50	ygl	bauzas: how to proceed now ?
10:31:58	bauzas	and given you only have one node, it told you that there were no other nodes
10:32:22	bauzas	ygl: like I said, you should look at *why* the compute is unable to spawn your instance before rescheduling it
10:32:24	ygl	bauzas: shall I restart the compute node and check ?
10:32:30	bauzas	stop restarting things :)
10:32:36	bauzas	and rather look at logs :)
10:33:08	bauzas	somewhere in the nova-compute log, you have an ERROR that triggers a reschedule
10:33:44	bauzas	you could look at the request-id again
10:35:55	ygl	bauzas: i cant find any error messages in nova-compute logs
10:36:20	bauzas	you're grepping ERROR right?
10:36:25	ygl	yes
10:36:32	bauzas	okay, instead of doing that
10:36:43	bauzas	take the request-id
10:37:00	bauzas	find that request-id in the conductor, and see when it calls the compute node
10:37:07	ygl	bauzas: u mean the instance-id ?
10:37:15	bauzas	no, the context req-id
10:37:26	bauzas	oh, you don't know what's this ?
10:37:55	ygl	bauzas: sorry, i dont know . is it the message id of rabbitmq u mean ?
10:37:57	bauzas	it's the request UUID that's generated for every request coming from the keystone middleware
10:38:20	bauzas	it's useful for tracking RPCs
10:38:31	ygl	bauzas:where can i capture that ?

Earlier   Later