Failed to start SLAPD and B&R operation failed in ansible
Bug #2017927 reported by
Kirti Singh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Kirti Singh |
Bug Description
Ldap conf is pointing to itself as the provider in sync-replication directive hence the restore is failing.
Getting the below error while executing ansible playbook for restore.
stdout: 'Starting SLAPD: Failed to start SLAPD.
affects: | update-manager (Ubuntu) → openldap (Ubuntu) |
affects: | openldap (Ubuntu) → starlingx |
Changed in starlingx: | |
assignee: | nobody → Kirti Singh (kirtis) |
Changed in starlingx: | |
status: | New → In Progress |
tags: | added: stx.9.0 stx.update |
Changed in starlingx: | |
importance: | Undecided → Medium |
To post a comment you must log in.
Appending to Bug Description (from review) https:/ /review. opendev. org/c/starlingx /ansible- playbooks/ +/882116
"In a Duplex system when backup is taken from
controller-1 and performed restore on controller-0, the
restore fails due to SLAPD failure.
SLAPD fails to start because, the backup file schema/ cn=config/ olcDatabase= {1}mdb. ldif defines ldaps:/ /controller- 0 in the sync(olcSyncrep l) parameter( directive) ."
/etc/ldap/
the value, provider=
replication-