Project

General

Profile

Actions

Bug #6196

closed

Upgrading Rudder from 2.10 to 2.11 nightly fails to properly set roles and configures psql password

Added by Nicolas CHARLES almost 10 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Matthieu CERDA
Category:
Packaging
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When upgrading from 2.10 to 2.11, my rudder server root can't log any messages
After a deep investigation, it doesn't contain any roles; so can't set the proper passwords

The issue is that we don't properly check the the LDAP is up and running (we check that it contains rudder, and if not skip all LDAP scripts)
We should rather check that LDAP is up and running, if not, complain loudly, if it is, check if rudder* is there, and if it is not, silently skip all rudder ldap script (as now)

Caution: is it possible that rudder-upgrade be run BEFORE rudder-slapd has been installed (first install of rudder server root)

Actions

Also available in: Atom PDF