Actions
Bug #17777
closed
Auto-archive gitRepo.git failure warning is not actionnable, should be info or debug
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
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.
Updated by François ARMAND over 4 years ago
- Status changed from New to In progress
Updated by François ARMAND over 4 years 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
Updated by François ARMAND over 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|d1b649423835f1dadb29b4910754758296a12b59.
Updated by François ARMAND over 4 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 4 years 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.
Actions