Actions
Bug #18952
closedNotifications issues prevent host to be destroyed
Difficulty:
Triaged:
Description
When a host doesn't have an owner set (it happened to me, when I created fake host via console,
the failure to send notification prevented the host to be destroyed and no useful message was provided:
everything seemed fine, except the host was still there.
I believe the failures in notifications should not influence the functionality of the operation itself.
2017-03-17T17:41:04 e59c76c5 [app] [D] Setting current user thread-local variable to admin 2017-03-17T17:41:04 e59c76c5 [user:admin] [app] [D] Setting current organization thread-local variable to none 2017-03-17T17:41:04 e59c76c5 [user:admin] [app] [D] Setting current location thread-local variable to none 2017-03-17T17:41:04 e59c76c5 [user:admin] [notifications] [W] Invalid owner for aaron-brangers, unable to send notifications 2017-03-17T17:41:04 e59c76c5 [user:admin] [notifications] [D] Notification event: Hosts::MissingOwner - checking for notifications 2017-03-17T17:41:04 e59c76c5 [user:admin] [app] [I] Failed to save: 2017-03-17T17:41:04 e59c76c5 [user:admin] [app] [I] Redirected to http://localhost:3000/hosts
Updated by The Foreman Bot almost 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/4387 added
Updated by Ivan Necas almost 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 54db95ae8230bdaa452094b52bc87c8bded69589.
Updated by The Foreman Bot almost 8 years ago
- Pull request https://github.com/theforeman/foreman/pull/4302 added
Updated by Ohad Levy over 7 years ago
- Translation missing: en.field_release set to 209
Updated by Marek Hulán over 7 years ago
- Related to Bug #19171: Notification about missing owner of a host is present after host which has been destroyed added
Actions