On Ubuntu 16.04, Bootstrap fails

[ubellavance]

Everything looks like it's doing fine...

Notice: /Stage[main]/Zendserver::Service/Service[zend-server]/ensure: ensure changed 'stopped' to 'running'

But...
Notice: /Stage[main]/Zendserver::Bootstrap::Exec/Exec[zend-server-init]/returns: Error: API error: Unable to Connect to tcp://localhost:10081. Error #111: Connection refused Error: /usr/local/zend/bin/zs-bootstrap-puppet.sh returned 1 instead of one of [0] Error: /Stage[main]/Zendserver::Bootstrap::Exec/Exec[zend-server-init]/returns: change from notrun to 0 failed: /usr/local/zend/bin/zs-bootstrap-puppet.sh returned 1 instead of one of [0]
If I look in the logs, it looks like the service has been stopped.
Notice: /Stage[main]/Zendserver::Service/Service[zend-server]/ensure: ensure changed 'stopped' to 'running' Notice: /Stage[main]/Zendserver::Bootstrap::Exec/Exec[zend-server-init]/returns: Error: API error: Unable to Connect to tcp://localhost:10081. Error #111: Connection refused Error: /usr/local/zend/bin/zs-bootstrap-puppet.sh returned 1 instead of one of [0] Error: /Stage[main]/Zendserver::Bootstrap::Exec/Exec[zend-server-init]/returns: change from notrun to 0 failed: /usr/local/zend/bin/zs-bootstrap-puppet.sh returned 1 instead of one of [0]
If I start the service manually, then run the bootstrap, it works.

[ubellavance]

It looks like it was working before my series of PRs, but I can't find where it broke.

[mkherlakian]

I've had that happen on the Chef cookbook as well. I think I got around it by waiting for the service to come up. I call the info endpoint on the api until I get a request, I retry 5 times and give up if I don't get anything back.

[ubellavance]

It looks like zend-server service is stopped completely somehow. I don't know why it's OK on RHEL...

[mkherlakian]

We'll need to execute with higher verbosity or review the logs. It's just not restarting after install it would seem.

[ubellavance]

Already looked at the logs. Didn't find anything except that a stop on the zend-server service seems to be called. It's not not restarted, it's just stop, for some reason. Is there a way to revert commits one by one? If I test the "original" module (not touched by me), the problem doesn't occur.

[ubellavance]

@mkherlakian please add the Ubuntu label to this ticket please