Closed johnpmitsch closed 4 years ago
This could have something to do with multiple puma processes that foreman start kicks off, perhaps since its using multiple PIDs the server.pid isn't created?
As a workaround, you can touch the tmp/pids/server.pid file on the katello box
When you spin up a
centos7-proxy-devel
box, it doesn't work withforeman start
.We check the
server.pid
file which is not created with foreman start, so the playbook fails because "no server is running"