Actions
Bug #16705
closed
Report compatibility mode does not seem to work with DSC agents
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
76
Name check:
To do
Fix check:
To do
Regression:
Description
In 6.0 with the report mode set on "HTTPS/Sylog" I loose all my reports from the windows nodes.
I believe this is a bug on the server/relay side since the reports are working fine in "Syslog only" mode
Updated by Félix DALLIDET about 4 years ago
- Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
Updated by Félix DALLIDET about 4 years ago
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 76
Updated by Félix DALLIDET about 4 years ago
Seems to work fine if there is o relay between the Rudder server and the agent
Updated by Nicolas CHARLES about 4 years ago
Actual issue is that we don't run the check_log_system bundle that defines the or @ for udp and tcp, so the relay doesn't have it defined
Updated by Nicolas CHARLES about 4 years ago
- Related to Bug #16710: In HTTPS + syslog mode, agents without the http support (like 5.0) don't have their syslog configured added
Updated by Nicolas CHARLES about 4 years ago
- Status changed from New to Rejected
Relay config fixed on #16710
Actions