Bug #5723: Rsyslog configuration lacks postgresql password on relay-top - Rudder - Issue Tracker

Custom queries

8.1 beta
Bugs triage
CS - by priority
CS - to review
My TR
Need technical review
Open bugs (all)
Open bugs (UI - UX)
Open UX defects (all)
Opened by users

Actions

Copy link

Bug #5723

closed

Rsyslog configuration lacks postgresql password on relay-top

Added by Benoît PECCATTE about 10 years ago. Updated almost 5 years ago.

Status:

Rejected

Priority:

Assignee:

Category:

Documentation

Target version:

4.1.24

Pull Request:

Severity:

Major - prevents use of part of Rudder | no simple workaround

UX impact:

User visibility:

Operational - other Techniques | Technique editor | Rudder settings

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

On relay-top, the system technique file distributePolicy/1.0/rsyslogConf.st generates /etc/rsyslog.d/rudder.conf without postgresql password.
This is a problem since multiserver setup will fail to transmit reports.

First the file containing the password is not copied from the webapp server. ( /opt/rudder/etc/rudder-passwords.conf )
Then the server-roles/1.0/password-check.cf use the class root_server instead of a class that includes the relay-top role.

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #6226: Document migration from manually installed relays

Released

Benoît PECCATTE

2015-02-04

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Jonathan CLARKE almost 10 years ago

Target version changed from 3.0.0~beta1 to 3.0.0~beta2

Actions

Copy link

Updated by François ARMAND almost 10 years ago

Target version changed from 3.0.0~beta2 to 3.0.0~rc1

Actions

Copy link

Updated by Vincent MEMBRÉ almost 10 years ago

Target version changed from 3.0.0~rc1 to 3.0.0

Actions

Copy link

Updated by Matthieu CERDA almost 10 years ago

Status changed from New to Discussion
Assignee set to François ARMAND
Priority changed from N/A to 2

First issue to address is: how do we distribute the passwords. We would need to build an acl for cf-serverd with the root server + relays ip addresses.

Maybe we need a system variable for this ?

Once it is done, the remaining part will be piece of cake :)

Anyone could suggest an approach here ? fanf of ncharles maybe ?

Actions

Copy link

Updated by Nicolas CHARLES almost 10 years ago

Passwords are stored in a specific files, with other password (ldap and webdav)
Since all passwords are stored in a file, it sounds dangerous to share this file on too more machine than necessary

We could use a system variable, but we'd have a nasty issue when changing the passwords: the promises would use old password (from promises), and webapp would be unable to regenerate new promises, as database would be unavailable - wrong password

This sounds like a complex problem, and the solution probably is "user must manage himself its password in distributed installation, with the help of easy to use documentation/scripts that explain what to do"

Actions

Copy link

Updated by François ARMAND almost 10 years ago

I agree with you comment Nicolas.

Benoit, could you document what is needed to do to make it works ?

I think the documentation must appear at the end of the package installation, so that the user is notified that he has something left to do. And the same documentation must be added in relay server installation http://www.rudder-project.org/rudder-doc-3.0/rudder-doc.html#relay-servers

Actually, the documentation for relay server is not up-to-date (see #6226)

Actions

Copy link

Updated by François ARMAND almost 10 years ago

Project changed from 24 to Rudder
Category changed from Techniques to Documentation

Actions

Copy link

Updated by François ARMAND almost 10 years ago

Target version changed from 3.0.0 to 3.1.0~beta1

So, to be more precise, that ticket will be studied in 3.1, and for 3.0 we are going to address #6226.

Actions

Copy link

Updated by Vincent MEMBRÉ over 9 years ago

Target version changed from 3.1.0~beta1 to 3.1.0~rc1

Actions

Copy link

#10

Updated by Vincent MEMBRÉ over 9 years ago

Target version changed from 3.1.0~rc1 to 3.1.0

Actions

Copy link

#11

Updated by Vincent MEMBRÉ over 9 years ago

Target version changed from 3.1.0 to 3.1.1

Actions

Copy link

#12

Updated by Vincent MEMBRÉ over 9 years ago

Target version changed from 3.1.1 to 3.1.2

Actions

Copy link

#13

Updated by Vincent MEMBRÉ about 9 years ago

Target version changed from 3.1.2 to 3.1.3

Actions

Copy link

#14

Updated by Vincent MEMBRÉ about 9 years ago

Target version changed from 3.1.3 to 3.1.4

Actions

Copy link

#15

Updated by Vincent MEMBRÉ about 9 years ago

Target version changed from 3.1.4 to 3.1.5

Actions

Copy link

#16

Updated by Vincent MEMBRÉ almost 9 years ago

Target version changed from 3.1.5 to 3.1.6

Actions

Copy link

#17

Updated by Vincent MEMBRÉ almost 9 years ago

Target version changed from 3.1.6 to 3.1.7

Actions

Copy link

#18

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 3.1.7 to 3.1.8

Actions

Copy link

#19

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 3.1.8 to 3.1.9

Actions

Copy link

#20

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 3.1.9 to 3.1.10

Actions

Copy link

#21

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 3.1.10 to 3.1.11

Actions

Copy link

#22

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 3.1.11 to 3.1.12

Actions

Copy link

#23

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 3.1.12 to 3.1.13

Actions

Copy link

#24

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 3.1.13 to 3.1.14

Actions

Copy link

#25

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 3.1.14 to 3.1.15

Actions

Copy link

#26

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 3.1.15 to 3.1.16

Actions

Copy link

#27

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 3.1.16 to 3.1.17

Actions

Copy link

#28

Updated by Vincent MEMBRÉ almost 8 years ago

Target version changed from 3.1.17 to 3.1.18

Actions

Copy link

#29

Updated by Vincent MEMBRÉ almost 8 years ago

Target version changed from 3.1.18 to 3.1.19

Actions

Copy link

#30

Updated by François ARMAND over 7 years ago

Severity set to Major - prevents use of part of Rudder | no simple workaround
User visibility set to Infrequent - complex configurations | third party integrations
Priority set to 0

Actions

Copy link

#31

Updated by Vincent MEMBRÉ over 7 years ago

Target version changed from 3.1.19 to 3.1.20

Actions

Copy link

#32

Updated by Jonathan CLARKE over 7 years ago

Status changed from Discussion to New

Actions

Copy link

#33

Updated by Jonathan CLARKE over 7 years ago

Assignee deleted (~~François ARMAND~~)

Actions

Copy link

#34

Updated by Vincent MEMBRÉ over 7 years ago

Target version changed from 3.1.20 to 3.1.21

Actions

Copy link

#35

Updated by Vincent MEMBRÉ over 7 years ago

Target version changed from 3.1.21 to 3.1.22

Actions

Copy link

#36

Updated by Benoît PECCATTE over 7 years ago

User visibility changed from Infrequent - complex configurations | third party integrations to Operational - other Techniques | Technique editor | Rudder settings
Priority changed from 0 to 30