Project

General

Profile

Actions

Bug #8197

closed

rudder-server-roles.conf doesn't have proper hostname

Added by Benoît PECCATTE about 8 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Server components
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
41
Name check:
Fix check:
Regression:

Description

The file /var/rudder/cfengine-community/inputs/rudder_server-roles.conf that is generated from a system technique contains hostnames for various roles.
These hostnames are generated from the webapp (&RUDDER_SERVER_ROLES&)

In case of a a server having roles but a local ldap server (distributed installation but ldap on the same machine as the webapp)
- the value configured in /opt/rudder/etc/rudder-web.properties is localhost
- the value generated in rudder_server-roles.conf is the full hostname of the machine
- the ldap server being local it only listen to 127.0.0.1

-> rudder-upgrade doesn't work since it takes the hostname from rudder_server-roles.conf


Related issues 1 (0 open1 closed)

Related to Rudder - Architecture #8463: Server roles is a BIG mess causing inconsistencies and bugsRejectedActions
Actions

Also available in: Atom PDF