[Build "Ubuntu 14.04.2 LTS" 3.0.2.0-35~kilo]:Glance api failed to start
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Fix Committed
|
Critical
|
Atul Moghe | |||
Trunk |
Fix Committed
|
Critical
|
Atul Moghe |
Bug Description
All sanity cases failed here as glance api failed to start
http://
logs saved at /cs-shared/
log
====
2016-05-11 08:08:43,775 INFO success: nova-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-05-11 08:08:43,775 INFO success: heat-engine entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-05-11 08:08:43,775 INFO success: glance-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-05-11 08:08:43,775 INFO success: heat-api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-05-11 08:08:43,775 INFO success: cinder-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-05-11 08:08:44,104 INFO exited: glance-api (exit status 1; not expected)
2016-05-11 08:08:44,111 INFO spawned: 'glance-api' with pid 8277
2016-05-11 08:08:44,750 INFO exited: glance-api (exit status 1; not expected)
2016-05-11 08:08:45,755 INFO spawned: 'glance-api' with pid 8364
2016-05-11 08:08:46,770 INFO success: glance-api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-05-11 08:08:47,580 INFO exited: glance-api (exit status 1; not expected)
2016-05-11 08:08:47,589 INFO spawned: 'glance-api' with pid 8515
2016-05-11 08:08:48,589 INFO success: glance-api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-05-11 08:08:48,799 INFO exited: glance-api (exit status 1; not expected)
2016-05-11 08:08:48,802 INFO spawned: 'glance-api' with pid 8531
2016-05-11 08:08:49,128 INFO exited: glance-api (exit status 1; not expected)
2016-05-11 08:08:50,318 INFO spawned: 'glance-api' with pid 8613
2016-05-11 08:08:50,620 INFO exited: glance-api (exit status 1; not expected)
2016-05-11 08:08:53,330 INFO spawned: 'glance-api' with pid 8720
2016-05-11 08:08:53,657 INFO exited: glance-api (exit status 1; not expected)
2016-05-11 08:08:57,366 INFO spawned: 'glance-api' with pid 8740
2016-05-11 08:08:58,027 INFO exited: glance-api (exit status 1; not expected)
2016-05-11 08:08:58,374 INFO gave up: glance-api entered FATAL state, too many start retries too quickly
2016-05-11 08:09:04,135 INFO stopped: glance-registry (terminated by SIGKILL)
2016-05-11 08:09:04,139 INFO spawned: 'glance-registry' with pid 9018
2016-05-11 08:09:05,641 INFO success: glance-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-05-11 08:09:05,771 INFO spawned: 'glance-api' with pid 9166
2016-05-11 08:09:06,230 INFO exited: glance-api (exit status 1; not expected)
2016-05-11 08:09:06,848 INFO stopped: keystone (terminated by SIGKILL)
2016-05-11 08:09:06,851 INFO spawned: 'keystone' with pid 9201
2016-05-11 08:09:07,310 INFO spawned: 'glance-api' with pid 9216
2016-05-11 08:09:07,617 INFO exited: glance-api (exit status 1; not expected)
2016-05-11 08:09:08,427 INFO success: keystone entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-05-11 08:09:10,045 INFO spawned: 'glance-api' with pid 9304
2016-05-11 08:09:10,362 INFO exited: glance-api (exit status 1; not expected)
2016-05-11 08:09:13,546 INFO spawned: 'glance-api' with pid 9401
2016-05-11 08:09:13,967 INFO exited: glance-api (exit status 1; not expected)
2016-05-11 08:09:14,364 INFO gave up: glance-api entered FATAL state, too many start retries too quickly
I am unable to create this problem on single box docker setup with a given image. Glance api works fine after fab setup_all. Though glance-manage db_sync gives similar warning during provisioning, That warning is due to deprecated api but should not make glance api service to die. Please recreate the problem and keep the setup in that state.