Actions
Bug #13664
closedError 500 when a host informs the foreman it is built but foreman can not send mails
Description
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:
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.
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.
Files
Updated by The Foreman Bot almost 9 years ago
- Status changed from New to Ready For Testing
- Assignee set to Shlomi Zadok
- Pull request https://github.com/theforeman/foreman/pull/3176 added
Updated by Shlomi Zadok almost 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset a90e4f2fe26529406220b24073d8052af7c5b67b.
Updated by Dominic Cleal almost 9 years ago
- Translation missing: en.field_release set to 71
Actions