Actions
Bug #18279
closed
Incorrect configuration when the database is not hosted on the rudder server itself
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
causing bad syslog/rudder-relayd configuration that forces localhsot
Updated by Nicolas CHARLES about 4 years ago
- Translation missing: en.field_tag_list set to Sponsored
Updated by Nicolas CHARLES about 4 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES about 4 years ago
- 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
Updated by Nicolas CHARLES about 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|812e2e95b58e98acecae5f66287819e79b3bdd66.
Updated by Alexis Mousset about 4 years ago
- 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
Updated by Alexis Mousset about 4 years ago
- Name check changed from To do to Reviewed
Updated by Alexis Mousset about 4 years ago
- 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
Updated by Alexis Mousset about 4 years ago
- Fix check changed from To do to Checked
It does not break server and worked in real life, considered checked.
Updated by Nicolas CHARLES about 4 years ago
- Related to Bug #16475: Postinst scripts do not set the postgres password added
Updated by Vincent MEMBRÉ about 4 years ago
- 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.
Actions