Actions
Bug #22642
closed
When using the external-db.conf to configure new instance postgresql password is still randomized during post install
Pull Request:
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.
Updated by 
Updated by
Actions