Bug #2321

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

Added by Nicolas CHARLES almost 3 years ago. Updated over 2 years ago.

Status:Released Start date:2012-02-23
Priority:3 Due date:
Assignee:Nicolas CHARLES % Done:

100%

Category:Webapp - Administration
Target version:2.4.0~beta5
Needs translating:No Pull Request:

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 ??

Associated revisions

Revision 61668cd7
Added by Nicolas CHARLES over 2 years ago

Fixes #2321 : Add proper logs for error in Historization of names

History

#1 Updated by Jonathan CLARKE over 2 years ago

  • Target version changed from 2.4.0~alpha6 to 2.3.8

#2 Updated by Jonathan CLARKE over 2 years ago

  • Target version changed from 2.3.8 to 2.3.9

#3 Updated by François ARMAND over 2 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.

#4 Updated by Nicolas CHARLES over 2 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

#5 Updated by Jonathan CLARKE over 2 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
  • 2 set to 0

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

#6 Updated by Nicolas CHARLES over 2 years ago

  • Status changed from 2 to In progress

#7 Updated by Nicolas CHARLES over 2 years ago

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

#8 Updated by François ARMAND over 2 years ago

  • Status changed from Pending technical review to Released
  • 2 changed from 0 to 1

That seems cool, thanks !

Also available in: Atom PDF