Actions
Bug #23849
closedCurrent user is not set when triggering repetitions of recurring actions
Difficulty:
Triaged:
Bugzilla link:
Description
They fail with undefined method id for nil, this is caused by two factors.
1) We rely on User.current always being set in here1
2) By moving the repetition triggering to a hook, it now runs outside of scope of the KeepCurrentUser middleware and therefore the current user is unset.
For people googling for the error, the issue can be identified by the following line in logs:
Failed to run hook 'trigger_repeat' for action 'Actions::RemoteExecution::RunHostsJob'
Updated by Adam Ruzicka over 6 years ago
- Project changed from Foreman Remote Execution to foreman-tasks
- Subject changed from Recurring REX jobs fail to trigger repetitions to Current user is not set when triggering repetitions of recurring actions
- Category deleted (
Foreman)
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Assignee set to Adam Ruzicka
- Pull request https://github.com/theforeman/foreman-tasks/pull/345 added
Updated by Adam Ruzicka over 6 years ago
- Pull request https://github.com/Dynflow/dynflow/pull/286 added
Updated by Ivan Necas over 6 years ago
- Related to Bug #21802: Recurring tasks need to be more resilient added
Updated by Ivan Necas over 6 years ago
- Status changed from Ready For Testing to Closed
Updated by Daniel Lobato Garcia over 6 years ago
- Translation missing: en.field_release set to 353
Updated by Daniel Lobato Garcia over 6 years ago
- Translation missing: en.field_release deleted (
353)
Updated by Adam Ruzicka over 6 years ago
- Related to Bug #24882: recurring jobs ignore organization context of host search added
Actions