Actions
Bug #16710
closed
In HTTPS + syslog mode, agents without the http support (like 5.0) don't have their syslog configured
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
We blindly assume that all is https, but agent 5.0 doesn't support them
so we should check for the "http" agent capability
It also has the side effect of breaking syslog on relays (see #16705)
Updated by Nicolas CHARLES about 4 years ago
- Related to Bug #16705: Report compatibility mode does not seem to work with DSC agents added
Updated by Nicolas CHARLES about 4 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES about 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Félix DALLIDET
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1582
Updated by Nicolas CHARLES about 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|e04347366236455b4cfe15f7db7d6c1c5fd39764.
Updated by Vincent MEMBRÉ about 4 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset about 4 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ about 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.3 which was released today.
Updated by Nicolas CHARLES over 3 years ago
- Related to Bug #18222: In HTTPS+Syslog, syslog config is not removed if agent supports https added
Actions