Actions
Bug #10343
closedActiveRecord::RecordNotSaved creating settings when Rails cache not functional
Description
When using foreman_memcache and it's unconfigured and not functional, then a new setting is added (e.g. installing a new plugin), app startup simply fails with "ActiveRecord::RecordNotSaved".
To reproduce, install foreman_memcache and another plugin which adds settings, then Foreman should fail to start.
Rails.cache.delete returns 'false' when the cache isn't functional. The Setting#clear_cache before_save callback then calls cache.delete, returning the result. This causes the saving of the setting to fail entirely.
Updated by Dominic Cleal over 9 years ago
- Status changed from New to Assigned
- Assignee set to Dominic Cleal
Updated by The Foreman Bot over 9 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2344 added
- Pull request deleted (
)
Updated by Dominic Cleal over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 83bd400ce6d69c8f946ff5ed31012ab073fcf1b1.
Updated by Dominic Cleal over 9 years ago
- Translation missing: en.field_release set to 50
Actions