Comment 6 for bug 1802971

Revision history for this message
Slawek Kaplonski (slaweq) wrote :

@Rabi: I don't think it's related as it is about different network.
Id of network used in failed test was: 783701e2-8acc-4cb8-ab8a-c7040f549475 and I found only logs like:

level=error msg="Handler for POST /v1.26/containers/create returned error: Conflict. The container name \"/neutron-dnsmasq-qdhcp-783701e2-8acc-4cb8-ab8a-c7040f549475\" is already in use by container fbc4bbc8f5d3ee398dd8e6637b33e466d1349e67742b6344c2c009cc169e2b4a. You have to remove (or rename) that container to be able to reuse that name."

in log file: http://logs.openstack.org/03/616203/9/gate/tripleo-ci-centos-7-standalone/75f1be5/logs/undercloud/var/log/journal.txt.gz#_Nov_12_17_29_13

I don't know if that is related or not as before this log it looks that proper container was spawned. And also first instance in test was configured fine, issue was only with second so IMO dhcp server worked properly at least for first instance.