Zaqar fails to start in heat gate tests

Bug #1544292 reported by Steven Hardy on 2016-02-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zaqar
Undecided
Unassigned

Bug Description

I'm seeing this:

2016-02-10 15:56:35.318 | + /opt/stack/new/devstack/functions-common:run_plugins:L1855: source /opt/stack/new/zaqar/devstack/plugin.sh stack extra
2016-02-10 15:56:35.361 |
2016-02-10 15:56:35.361 | [uwsgi]
2016-02-10 15:56:35.361 | add-header = Connection: close
2016-02-10 15:56:35.361 | master = true
2016-02-10 15:56:35.361 | callable = app
2016-02-10 15:56:35.361 | wsgi-file = /opt/stack/new/zaqar/zaqar/transport/wsgi/app.py
2016-02-10 15:56:35.361 | threads = 4
2016-02-10 15:56:35.361 | processes = 1
2016-02-10 15:56:35.361 | harakiri = 60
2016-02-10 15:56:35.361 | http = 127.0.0.1:8888
2016-02-10 15:56:35.397 | Waiting for Zaqar to start...
2016-02-10 15:57:40.235 | [Call Trace]
2016-02-10 15:57:40.235 | ./stack.sh:1330:run_phase
2016-02-10 15:57:40.235 | /opt/stack/new/devstack/functions-common:1888:run_plugins
2016-02-10 15:57:40.235 | /opt/stack/new/devstack/functions-common:1855:source
2016-02-10 15:57:40.235 | /opt/stack/new/zaqar/devstack/plugin.sh:266:start_zaqar
2016-02-10 15:57:40.235 | /opt/stack/new/zaqar/devstack/plugin.sh:211:die
2016-02-10 15:57:40.241 | [ERROR] /opt/stack/new/zaqar/devstack/plugin.sh:211 Zaqar did not start

here:
https://review.openstack.org/#/c/274101/

However screen-zaqar-wsgi.txt.gz isn't showing an obvious error:

2016-02-10 15:58:50.037 27275 WARNING oslo_config.cfg [-] Option "username" from group "keystone_authtoken" is deprecated. Use option "user-name" from group "keystone_authtoken".
2016-02-10 15:58:50.038 27275 WARNING keystonemiddleware.auth_token [-] signing_dir mode is 0755 instead of 0700
2016-02-10 15:58:50.039 27275 WARNING oslo_config.cfg [-] Option "memcache_servers" from group "keystone_authtoken" is deprecated. Use option "memcached_servers" from group "keystone_authtoken".
WSGI app 0 (mountpoint='') ready in 3 seconds on interpreter 0x18ef710 pid: 27275 (default app)
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 27275)
spawned uWSGI worker 1 (pid: 27333, cores: 4)
spawned uWSGI http 1 (pid: 27334)
[pid: 27333|app: 0|req: 1/1] 127.0.0.1 () {32 vars in 426 bytes} [Wed Feb 10 15:58:58 2016] GET /v2/ping => generated 95 bytes in 4815 msecs (HTTP/1.1 400) 3 headers in 99 bytes (1 switches on core 0)
[pid: 27333|app: 0|req: 2/2] 127.0.0.1 () {32 vars in 426 bytes} [Wed Feb 10 15:59:04 2016] GET /v2/ping => generated 95 bytes in 3 msecs (HTTP/1.1 400) 3 headers in 99 bytes (1 switches on core 1)
...

Rabi Mishra (rabi) wrote :

This is possibly fixed by https://review.openstack.org/#/c/492123/. I've not seen this issue since that landed.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers