Bug #15861
closed
audited_changes column is too small
Description
I had an issue this morning when updating a quite long param in foreman:
Data too long for column 'audited_changes' at row 1
A simple fix to this problem was to hack into foreman DB and run "ALTER TABLE audits MODIFY audited_changes MEDIUMTEXT;"
Thanks.
Updated by Dominic Cleal over 8 years ago
- Category set to Audit Log
The column should be a Rails "text" type, which IIRC is 64k, but the field would probably contain the parameter value and similar info.
Updated by Joe Mader almost 8 years ago
I've run into this same scenario. We don't use a "sideband" CM platform for tracking host metadata and thus some of our host-specific parameter values stored in the Foreman DB are rather large.
I was not able to conveniently locate an "admin-facing" tunable which could either turn auditing off or otherwise "filter" what gets audited.
Coincidentally, we resorted to changing the "audited_changes" column type to MEDIUMTEXT as a testing workaround. My concern is that this approach is not quite "future proof" (easily superceded by an upstream rails DB migration). Are there notable objections to making MEDIUMTEXT the new default? Given that there appears to be no fulltext index on this column, Foreman system owners would just need to ensure sufficient filesystem storage.
Updated by The Foreman Bot over 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/4556 added
Updated by Amir Fefer over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset cf4687537819e1862d530049a7f29d0e86ba16fe.
Updated by Marek Hulán over 7 years ago
- Translation missing: en.field_release set to 240