Project

General

Profile

Bug #16002

When switching to HTTPS reporting, the compliance of root server is broken because it receives both https and syslog

Added by Nicolas CHARLES about 1 month ago. Updated 16 days ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

when switching to "HTTPS with syslog support for migration purpose (old agent or legacy systems)", compliance of root server is broken as we receive both https and syslog reporting

Associated revisions

Revision 8d289879 (diff)
Added by Nicolas CHARLES about 1 month ago

Fixes #16002: When switching to HTTPS reporting, the compliance of root server is broken because it receives both https and syslog

History

#1

Updated by Nicolas CHARLES about 1 month ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
#2

Updated by Nicolas CHARLES about 1 month ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1539
#3

Updated by Nicolas CHARLES about 1 month ago

  • Status changed from Pending technical review to Pending release
#4

Updated by Vincent MEMBRÉ 16 days ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.0.0~beta1 which was released today.

Also available in: Atom PDF