Bug #16464
closed
Upgrade fails because we try to insert an LDAP property that is already there
Added by Félix DALLIDET almost 5 years ago.
Updated almost 5 years ago.
Category:
Server components
Description
In the webapp postinst we are executing rudder-upgrade, even after a fresh install.
Install fails with the following error:
ldap_add: Already exists (68)
Starting from 6.0.1 we are setting default protocol if not set.
But it seems like we are trying to set it only if it was already set-up instead of when it is missing.
- Status changed from New to In progress
- Assignee set to Félix DALLIDET
- Status changed from In progress to Pending technical review
- Assignee changed from Félix DALLIDET to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2173
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
- Subject changed from Nightlies fail to install since rudder-upgrade always fail on postinst to Upgrade fails because we try to insert an LDAP property that is already there
- Name check changed from To do to Reviewed
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.2 which was released today.
Also available in: Atom
PDF