Project

General

Profile

Actions
Copy link

Bug #8177

closed

Broken rudder-server-roles.conf prevent reporting in distributed setup

Added by Vincent MEMBRÉ about 8 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
1
Assignee:
François ARMAND
Category:
Web - Config management
Target version:
3.2.2
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Since rudder 3.2 we don't produce valid rudder-server-roles.conf files

For each role, we assign their key in the config file, not the value from the config file or the computed one

They all look like this:

# role:hostname1,hostname2,hostname3
rudder-ldap:rudder.server-roles.ldap
rudder-inventory-endpoint:rudder.server-roles.inventory-endpoint
rudder-db:rudder.server-roles.db
rudder-relay-top:rudder.server-roles.relay-top
rudder-web:rudder.server-roles.web
rudder-relay-promises-only:rudder.server-roles.relay-promises-only
rudder-cfengine-mission-portal:rudder.server-roles.cfengine-mission-portal

in AppConfig.scala we should replace:

RudderServerRole("rudder-ldap", "rudder.server-roles.ldap")

by:

RudderServerRole("rudder-ldap", config.getString("rudder.server-roles.ldap"))

Related issues 1 (0 open — 1 closed)

Related to Rudder - User story #7342: Adapt the logic in Rudder to handle the two new rolesReleasedFrançois ARMAND2015-10-30Actions
Actions
Copy link

Also available in: Atom PDF