Project

General

Profile

Actions
Copy link

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.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Server components
Target version:
6.0.2
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:

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.

Actions
Copy link
 #1

Updated by Félix DALLIDET almost 5 years ago

  • Status changed from New to In progress
  • Assignee set to Félix DALLIDET
Actions
Copy link
 #2

Updated by Félix DALLIDET almost 5 years ago

  • 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
Actions
Copy link
 #3

Updated by Félix DALLIDET almost 5 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #4

Updated by François ARMAND almost 5 years ago

  • Fix check changed from To do to Checked
Actions
Copy link
 #5

Updated by Alexis Mousset almost 5 years ago

  • 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
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.0.2 which was released today.

Actions
Copy link

Also available in: Atom PDF