Actions
Bug #23206
closedBug #23186: Rudder Server 7.3.4 doesn't install on SLES 15 SP4
parent ticket doesn't work with a remote database
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Error - Fixed
Regression:
No
Description
with a remote file configured as followed, it says
# Please fill the configuration to make sure Rudder serveur will be properly installed # Please ask your database administrator for those informations. # Some commands are provided in case you need them. # Host where rudder server must connect to access the database DB_HOST="192.168.51.2" # Database user and password, to create them ask your database administrator or use the following command # su postgres -c "psql -q -c \"CREATE USER ${DB_USER} WITH PASSWORD '${DB_PASSWORD}'\"" DB_USER="rudder" DB_PASSWORD="rudder" # Postgresql database name, to create it ask your database administrator or use the following command # su postgres -c "psql -q -c \"CREATE DATABASE ${DB_NAME} WITH OWNER = ${DB_USER} ENCODING = UTF8\"" DB_NAME="rudder" # - true if your database administrator has already created the database structure # in this case please send you database administrator the provided schema (/opt/rudder/etc/postgresql/reportsSchema-ext.sql) # so that he can create it before you install rudder server # - false to let rudder setup populate the database (provided that DB_USER has the permission to do so) DB_IS_POPULATED="false"
ed Aug 2 17:21:00 CEST 2023 - Starting rudder-reports post installation step Wed Aug 2 17:21:00 CEST 2023 - Starting local database management Found postgres service name: postgresql Editing PG_HBA file /var/lib/pgsql/data/pg_hba.conf Created symlink /etc/systemd/system/multi-user.target.wants/postgresql.service -> /usr/lib/systemd/system/postgresql.service. Wed Aug 2 17:21:05 CEST 2023 - Populate the database at localhost Wed Aug 2 17:21:06 CEST 2023 - Ending rudder-reports post installation step Wed Aug 2 17:21:06 CEST 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 -> /usr/lib/systemd/system/rudder-jetty.service. Created symlink /etc/systemd/system/rudder-server.service.requires/rudder-jetty.service -> /usr/lib/systemd/system/rudder-jetty.service. Created symlink /etc/systemd/system/multi-user.target.wants/rudder-slapd.service -> /usr/lib/systemd/system/rudder-slapd.service. Created symlink /etc/systemd/system/rudder-server.service.requires/rudder-slapd.service -> /usr/lib/systemd/system/rudder-slapd.service. Created symlink /etc/systemd/system/multi-user.target.wants/rudder-server.service -> /usr/lib
Updated by Nicolas CHARLES over 1 year ago
detection of remote database is based only on rudder-web.properties which is not yet defined at first install
We should look also for EXTERNAL_DB_CONF file existance, and its content
Updated by Nicolas CHARLES over 1 year ago
- Status changed from New to In progress
Updated by Nicolas CHARLES over 1 year 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-packages/pull/2796
Updated by Nicolas CHARLES over 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|3468511037e050fb42028f163b4927494431c3e8.
Updated by Nicolas CHARLES over 1 year ago
- Fix check changed from To do to Error - Fixed
Updated by Alexis Mousset over 1 year ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.5 which was released today.
Actions