Bug #13664
Updated by Julien Pivotto about 8 years ago
When the foreman email is not properly configured, and a host is provisioned, it gets a 500 error when informing Foreman that it is built.
Attached the production.log in this ticket.
In the kickstart logs:
<pre>
Informing Foreman that we are built
--2016-02-11 10:57:40-- http://172.22.110.154/unattended/built?token=fgcfa081-a398-4333-b351-d3af03c0f3921
Connecting to 172.22.110.154:80... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2016-02-11 10:57:42 ERROR 500: Internal Server Error.
</pre>
Still the host is marked as built, as expected.
Expected behavior:
It logs in production.log that it can not send the email but returns 200. I do not want my host to be rebuild in a loop just because email can not be sent.