Project

General

Profile

Actions
Copy link

Bug #2699

closed

Upgrading from Rudder 2.3.8 to Rudder 2.4.0~beta3 fail at rudder-inventory-ldap stage (Debian Squeeze 64bits)

Added by Nicolas PERRON over 12 years ago. Updated almost 10 years ago.

Status:
Rejected
Priority:
1 (highest)
Assignee:
Nicolas PERRON
Category:
Packaging
Target version:
2.4.0~beta3
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

On Debian Squeeze 64 bits, when trying to upgrade from Rudder 2.3.8 to 2.4.0~beta3 an error message is displayed about LDAP by aptitude before to stop.

# aptitude upgrade
[...]
The Rudder OpenLDAP schema is not up to date.
You will see some warnings about UNKNOWN attributeDescription.
Updating...
...done.
slapd[3131]: [INFO] Using /etc/default/slapd for configuration
slapd[3136]: [INFO] Killing OpenLDAP with force...
slapd[3138]: [OK] slapd process killed with force (PID 2274)
slapd[3139]: [INFO] Killing OpenLDAP replication with force...
slapd[3145]: [INFO] Found no slurpd process running
501000e0 Entry (nodeId=root,ou=Nodes,cn=rudder-configuration), attribute 'nodeHostname' not allowed
slapadd: dn="nodeId=root,ou=Nodes,cn=rudder-configuration" (line=397): (65) attribute 'nodeHostname' not allowed
_                       2.68% eta    03s elapsed            none spd 193.8 k/s 
Closing DB...
dpkg: error processing rudder-inventory-ldap (--configure):
 subprocess installed post-installation script returned error exit status 1
[...]

It could be due to a migration in the LDAP entries to do.

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #2701: After a migration from 2.3.8 to 2.4.0~beta3, rudder can't search for itself in Node Management => Search NodesReleasedNicolas PERRON2012-07-25Actions
Actions
Copy link
 #1

Updated by Nicolas PERRON over 12 years ago

I think that's because there is two nodeId entries in LDAP:
  • nodeId=root,ou=Nodes Configuration,ou=Rudder,cn=rudder-configuration
  • nodeId=root,ou=Nodes,cn=rudder-configuration
The first one contains a lot of attributes like "nodeHostname" and the second one only contains:
  • cn
  • isBroken
  • isSystem
  • nodeId
  • description

So, the first entry must have been copied to the second one and it doesn't work. I will investigate more but If I can have some help, it would be great.

Actions
Copy link
 #2

Updated by Nicolas PERRON over 12 years ago

This issue is related to #2701 : nodeId=root,ou=Nodes,cn=rudder-configuration is not a new entry but it has too many attributes which result in a fail of rudder-inventory-ldap

Actions
Copy link
 #3

Updated by Nicolas PERRON over 12 years ago

  • Status changed from New to Rejected

Nicolas PERRON wrote:

This issue is related to #2701 : nodeId=root,ou=Nodes,cn=rudder-configuration is not a new entry but it has too many attributes which result in a fail of rudder-inventory-ldap

As explained above, this is related to #2701. This is a a duplicate in fact so I rejected this issue.

Actions
Copy link
 #4

Updated by Nicolas PERRON almost 12 years ago

  • Project changed from Rudder to 34
  • Category deleted (11)
Actions
Copy link
 #5

Updated by Benoît PECCATTE almost 10 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions
Copy link

Also available in: Atom PDF