Keystone fails to start due to a port conflict during gate-tempest test.

Bug #1203905 reported by Clark Boylan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
Triaged
High
James E. Blair

Bug Description

http://logs.openstack.org/23/36923/3/gate/gate-tempest-devstack-vm-postgres-full/34238/console.html and http://logs.openstack.org/23/36923/3/gate/gate-tempest-devstack-vm-postgres-full/34238/logs/screen-key.txt.gz capture a test run that failed because keystone ran into a port conflict. The running theory is that two devstack gate jobs were run on the same host leaving an old keystone process behind that was still bound to the keystone port. http://paste.openstack.org/show/41313/ seems to support this.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.