Project

General

Profile

Actions

Bug #2321

closed

If an error occurs during the name historization, there are no information about it except in the log

Added by Nicolas CHARLES about 12 years ago. Updated over 11 years ago.

Status:
Released
Priority:
3
Category:
Web - Maintenance
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I seem to recall it was a deliberate choice to accept that it could fail and not prevent normal execution. However, except by looking at the logs, there are no way to know that something went bad.

Maybe some monitoring in the log could warn the administrator ??

Actions #1

Updated by Jonathan CLARKE almost 12 years ago

  • Target version changed from 2.4.0~alpha6 to 2.3.8
Actions #2

Updated by Jonathan CLARKE over 11 years ago

  • Target version changed from 2.3.8 to 2.3.9
Actions #3

Updated by François ARMAND over 11 years ago

  • Status changed from New to Discussion
  • Assignee changed from François ARMAND to Nicolas CHARLES

Nicolas, could you tell me more about that one ? I think I don't understand it.

Actions #4

Updated by Nicolas CHARLES over 11 years ago

When we change names of groups, directives, rules, or their content, they are historised in the SQL databases for tracability during deployment of promises
However, if for some reason their historization fails, there is nothing except in the logs that will warn that the historization failed.
It's better that it's not blocking (why would we prevent deployment because a name cannot be stored in database), but a bit of information would help
Probably the new sysadmin logger would be useful in this case

Actions #5

Updated by Jonathan CLARKE over 11 years ago

  • Status changed from Discussion to 2
  • Priority changed from N/A to 3
  • Target version changed from 2.3.9 to 2.4.0~beta5

This information should be put in the ops log. This won't be fixed in 2.3.

Actions #6

Updated by Nicolas CHARLES over 11 years ago

  • Status changed from 2 to In progress
Actions #7

Updated by Nicolas CHARLES over 11 years ago

  • Status changed from In progress to Pending technical review
  • % Done changed from 0 to 100
Actions #8

Updated by François ARMAND over 11 years ago

  • Status changed from Pending technical review to Released

That seems cool, thanks !

Actions

Also available in: Atom PDF