Project

General

Profile

Actions

Bug #22642

closed

When using the external-db.conf to configure new instance postgresql password is still randomized during post install

Added by Richard dort about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Packaging
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I dislike using that feature
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
132
Name check:
To do
Fix check:
To do
Regression:
Yes

Description

I have been trying to automate the install and configuration of a rudder server and have noticed that when i use the external-db.conf the install will move along fine but during the post install script it will still randomize the passwords saved in /root/.pgpass and /opt/rudder/etc/rudder-passwords.conf causing the DB upgrade to fail and rudder-jetty to fail to restart after. I confirm this by validating the password in the external-db.conf does not match the password in the other 2 files but if i update them with the correct passwords jetty will start.

==> /var/log/rudder/install/rudder-server-20230406040346.log <==
Thu Apr  6 04:03:46 UTC 2023 - Starting rudder-server post installation script
Thu Apr  6 04:03:46 UTC 2023 - Starting rudder-reports post installation step
Thu Apr  6 04:03:46 UTC 2023 - Ending rudder-reports post installation step
Thu Apr  6 04:03:46 UTC 2023 - Starting rudder-webapp post installation step
Creating rudder users
Stopping apache before running upgrade scripts
Managing services
Created symlink /etc/systemd/system/multi-user.target.wants/rudder-jetty.service → /lib/systemd/system/rudder-jetty.service.
Created symlink /etc/systemd/system/rudder-server.service.requires/rudder-jetty.service → /lib/systemd/system/rudder-jetty.service.
Created symlink /etc/systemd/system/multi-user.target.wants/rudder-slapd.service → /lib/systemd/system/rudder-slapd.service.
Created symlink /etc/systemd/system/rudder-server.service.requires/rudder-slapd.service → /lib/systemd/system/rudder-slapd.service.
Created symlink /etc/systemd/system/multi-user.target.wants/rudder-server.service → /lib/systemd/system/rudder-server.service.
Initializing filesystem
Initializing git
Initialized empty shared Git repository in /var/rudder/configuration-repository/.git/
Upgrading techniques
Correctly set option autoupdate-technique-library to value true
Configuring LDAP

SUMMARY OF OPTIONS:

Allowed networks: 10.0.1.75/24
Force LDAP reset: no

Initializing LDAP database... done.

Updating Rudder password file with random passwords...  done.
Cleaning up temporary directories... done.

Reinitialization complete.

Related issues 1 (0 open1 closed)

Is duplicate of Rudder - Bug #22608: rudder-init replaces rudder-db password at postinstReleasedAlexis MoussetActions
Actions #1

Updated by François ARMAND about 1 year ago

  • Category set to Packaging
  • Target version set to 7.2.6
  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • UX impact set to I dislike using that feature
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 132
  • Regression changed from No to Yes
Actions #2

Updated by Benoît PECCATTE about 1 year ago

Hi Richard, it looks we just fixed this bug : https://issues.rudder.io/issues/22608

If this is the case, the next patch release will contain the fix.

Actions #3

Updated by Benoît PECCATTE about 1 year ago

  • Is duplicate of Bug #22608: rudder-init replaces rudder-db password at postinst added
Actions #4

Updated by Benoît PECCATTE about 1 year ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF