Actions
Bug #19148
closed
Parsing error when the port is undefined in change-validation.conf
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
51
Name check:
To do
Fix check:
To do
Regression:
Description
An error occurred when a change-request is created, when we try to send an email notification, the port is not configured by default in change-validation.conf so the parsing fail.
By adding a default port in the file, we prevent the parsing from failling and blocking the usual process without email notification.
Updated by Elaad FURREEDAN about 3 years ago
- Copied from Bug #18875: Error when parsing change-validation.conf file added
Updated by Elaad FURREEDAN about 3 years ago
- Status changed from New to In progress
Updated by Elaad FURREEDAN about 3 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Elaad FURREEDAN to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder-plugins/pull/361
Updated by Anonymous about 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder:rudder-plugins|5b85d7aa41073b253168c9e47ca1a7739540889b.
Updated by Vincent MEMBRÉ almost 3 years ago
- Status changed from Pending release to Released
- Priority changed from 52 to 51
This bug has been fixed in Rudder 6.1-1.10 which was released today.
Actions