Actions
Bug #18875
closed
Error when parsing change-validation.conf file
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:
47
Name check:
To do
Fix check:
To do
Regression:
Description
OS: Debian 6
Rudder version : 6.2.2
Plugin version: 6.2-1.10.0
All change validation status are enable
When I try to create a new rule, when a I save, a pop up to confirm the creation of the change request, but when we confirm a new pop saying that the server was not reachable
The server cannot be contacted at this time
I was not able to save the rule.
It seems like a parsing error of /opt/rudder/etc/plugins/change-validation.conf (see error.log file)
Files
Updated by Elaad FURREEDAN about 3 years ago
- Status changed from New to In progress
- Assignee set to Elaad FURREEDAN
Updated by Elaad FURREEDAN about 3 years ago
- Status changed from In progress to New
Updated by Elaad FURREEDAN about 3 years ago
- Target version changed from 6.1-1.10 to 6.2-1.11
Updated by Elaad FURREEDAN about 3 years ago
- Status changed from New to Pending technical review
- Assignee changed from Elaad FURREEDAN to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder-plugins/pull/353
Updated by Anonymous about 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder:rudder-plugins|3630f7851314060aecb004c41bcb6aab4194de32.
Updated by Anonymous about 3 years ago
Applied in changeset rudder:rudder-plugins|742f8ef3efd5a6f23b3aa96d307430aa10592582.
Updated by Elaad FURREEDAN about 3 years ago
- Copied to Bug #19148: Parsing error when the port is undefined in change-validation.conf added
Updated by Vincent MEMBRÉ over 2 years ago
- Status changed from Pending release to Released
- Priority changed from 52 to 47
Actions