Actions
Bug #12478
closedError during upgrade from 4.2 to 4.3 in stretch
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
*** slapd.conf (Y/I/N/O/D/Z) [default=N] ? Installing new version of config file /etc/init.d/rudder-slapd ... INFO: Restarting syslogd... Done INFO: Restarting rudder-slapd...5ad672f9 lt_dlopenext failed: (back_hdb.la) file not found slapcat: bad configuration file! <161>Apr 17 22:19:37 rudder-slapd[9455]: [ALERT] OpenLDAP database backup failed dpkg: error processing package rudder-inventory-ldap (--configure): subprocess installed post-installation script returned error exit status 1
Fixed by an "apt install -f" at the end of upgrade.
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.3.1 to 4.3.2
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.3.2 to 410
Updated by Benoît PECCATTE over 6 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Priority changed from 0 to 32
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 410 to 4.3.2
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.3.2 to 4.3.3
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.3.3 to 4.3.4
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.3.4 to 4.3.5
- Priority changed from 32 to 31
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.3.5 to 4.3.6
- Priority changed from 31 to 30
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.3.6 to 4.3.7
Updated by François ARMAND about 6 years ago
- Status changed from New to Rejected
- Priority changed from 30 to 0
I'm closing that one because we didn't experienced similar problem when testing upgrade from 4.1 to 4.3 or 5.0. As 4.2 is not supported anymore, it may have been something specific with the tested version.
Actions