Project

General

Profile

Bug #17777

Auto-archive gitRepo.git failure warning is not actionnable, should be info or debug

Added by François ARMAND 3 months ago. Updated 2 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

We often have a warning log:

Auto-archive gitRepo.git failure: not found in gitRepo.git added files: '......'. You can safely ignore that warning if the file was already existing in gitRepo.git and was not modified by that archive.

This has none piece of information for an user, who just see a warning in log that he doesn't understand. Even for us developer, we are not sure of the goal: is it a warning, or expected? What should be done in either case?

Baring a better message, it should be debug level.

#1

Updated by François ARMAND 3 months ago

  • Status changed from New to In progress
#2

Updated by François ARMAND 3 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/3083
#3

Updated by François ARMAND 3 months ago

  • Status changed from Pending technical review to Pending release
#5

Updated by Vincent MEMBRÉ 2 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.18 and 6.1.2 which were released today.

Also available in: Atom PDF