Bug #14954: Stop auditing the default field in settings - Foreman

Custom queries

3.10.0 release DONE
3.10.0 release TODO
3.11.0 release DONE
3.11.0 release TODO
3.8.1 release DONE
3.8.1 release TODO
3.9.2 release DONE
3.9.2 release TODO
All bugs by votes
All issues closed in the last 3 weeks
Easy and Trivial Issues
Easy Issues (only)
Foreman - new open issues in last 10 days
Good first issues - Foreman core
high prio open bugs
Host registration [open]
Mine
My issues closed in the last 3 weeks
old bugs
Open with target version set (aka blockers)
registration
taken-none
Team Atlas untriaged bugs
templates
Trivial Issues
Untriaged and opened in the past two weeks

Actions

Copy link

Bug #14954

closed

Stop auditing the default field in settings

Added by Shimon Shtein about 8 years ago. Updated almost 3 years ago.

Status:

Rejected

Priority:

Normal

Assignee:

Shimon Shtein

Category:

Settings

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

This field cannot be set by the user, and not every change to this field changes the behavior of the system.

Related issues 1 (0 open — 1 closed)

Related to Foreman - Bug #13574: Plugins with Setting subclasses raise super: no superclass method `load_defaults' error

Closed

Dominic Cleal

02/05/2016

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Dominic Cleal about 8 years ago

Related to Bug #13574: Plugins with Setting subclasses raise super: no superclass method `load_defaults' error added

Actions

Copy link

Updated by Dominic Cleal about 8 years ago

Category set to Settings
Status changed from New to Assigned

If some updates to the default value change the behaviour, then that seems reason enough to audit it.

Actions

Copy link

Updated by Shimon Shtein about 8 years ago

I have a case (downstream theme) where a plugin wants to change the default. This causes ping-pong updates with foreman core each system start and everything since it's audited, I have two audit messages for each setting.

Actions

Copy link

Updated by Anonymous almost 7 years ago

Shimon, what's the status here?

Actions

Copy link

Updated by Iain Walmsley over 6 years ago

I can confirm this is still an issue in 1.15.2, this proves to create an excessive amount of spam in the audits when there are multiple Foreman in a cluster which swamps the useful auditing that takes place.

Actions

Copy link