Bug #18279
closed
Incorrect configuration when the database is not hosted on the rudder server itself
Added by Nicolas CHARLES about 4 years ago.
Updated over 2 years ago.
Category:
System techniques
Description
causing bad syslog/rudder-relayd configuration that forces localhsot
- Translation missing: en.field_tag_list set to Sponsored
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
- 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/1629
- Status changed from Pending technical review to Pending release
- Subject changed from When the database is not hosted on the rudder server itself, the configuration set by techniques is invalid to Incorrect confgiuration when the database is not hosted on the rudder server itself
- Name check changed from To do to Reviewed
- Subject changed from Incorrect confgiuration when the database is not hosted on the rudder server itself to Incorrect configuration when the database is not hosted on the rudder server itself
- Fix check changed from To do to Checked
It does not break server and worked in real life, considered checked.
- Related to Bug #16475: Postinst scripts do not set the postgres password added
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.6 and 6.2.0~beta1 which were released today.
Also available in: Atom
PDF