Project

General

Profile

Actions
Copy link

Bug #16557

closed

Alerts do not trigger for empty configuration change descriptions

Added by Marcos M 4 months ago. Updated 28 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Marcos M
Category:
Configuration Backend
Target version:
2.9.0
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
26.03
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

A user notice is supposed to trigger when a configuration change is written but a description is not specified. This does not happen if the description is an empty string. This currently happens e.g. when changes are saved in the FRR package.

Actions
Copy link
 #1

Updated by Marcos M 4 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Applied in changeset commit:09aedfb18eb81663b2fc72d968fa0df0690fb3ca.

Actions
Copy link
 #2

Updated by Georgiy Tyutyunnik 4 months ago

  • Status changed from Feedback to Resolved

Log entries for config change with null description much more informative after the change:

25.07.1 FRR ACL change:
Nov 28 12:09:05 php-fpm 90646 /pkg_edit.php: Configuration Change:
26.03.a.20251128.0600 FRR ACL change:
Nov 28 12:06:14 php-fpm 622 NOTICE [Config] Configuration Change: (Local Database): FRR: changed ACLs

tested on:
26.03-DEVELOPMENT (amd64)
built on Fri Nov 28 6:00:00 UTC 2025
FreeBSD 16.0-CURRENT

Actions
Copy link
 #3

Updated by Jim Pingle 28 days ago

  • Subject changed from Alerts do not trigger for empty config change descriptions to Alerts do not trigger for empty configuration change descriptions
Actions
Copy link

Also available in: Atom PDF