Project

General

Profile

Actions

Bug #16295

closed

Bug #16294: Set HTTP reporting protocol by default on new rudder 6.0 installation

Keep syslog reporting when migrating from rudder 5.0

Added by François ARMAND about 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:

Description

Parent ticket changed the default reporting protocol. But for user with existing Rudder 5.0, we want to keep syslog.

So we need to set the correct rudder (LDAP) property before first boot of rudder 6.0 with a migration script.

The setting is controlled by rudder_report_protocol_default rudder setting and it must have value SYSLOG
The LDAP entry is:

dn: propertyName=rudder_report_protocol_default,ou=Application Properties,cn=rudder-configuration
objectClass: property
objectClass: top
propertyName: rudder_report_protocol_default
propertyValue: SYSLOG

Related issues 1 (0 open1 closed)

Has duplicate Rudder - Architecture #16195: Use HTTPS for reporting by default for new installsResolvedActions
Actions #1

Updated by Benoît PECCATTE about 5 years ago

  • Status changed from New to In progress
Actions #2

Updated by Benoît PECCATTE about 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/2154
Actions #3

Updated by Benoît PECCATTE about 5 years ago

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

Updated by François ARMAND about 5 years ago

Actions #5

Updated by Alexis Mousset about 5 years ago

  • Status changed from Pending release to Released

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

Actions

Also available in: Atom PDF