Bug #5280
closed
When the ldap tree changes, Rudder can't always access new info after an update
Added by Nicolas CHARLES over 10 years ago.
Updated over 9 years ago.
Category:
System integration
Description
Upgrading to 2.10 to 2.11, on a Centos6.5, cause the server not to have any roles
Regenerating inventories don't solve the issue, the inventory has the role, but it doesn't show up in the webapp
Reindexing the slapd fixes the issue
- Target version changed from 2.11.1 to 2.11.2
- Assignee set to Matthieu CERDA
Running /etc/init.d/rudder-slapd reindex solves the issue
- Status changed from New to Discussion
- Assignee changed from Matthieu CERDA to Nicolas CHARLES
- Priority changed from N/A to 2
Hmmmm, I am unable to reproduce this on a CentOS 6 machine:
- Installed Rudder 2.10.3
- Upgraded to Rudder 2.11.1
=> Roles are not here yet (Role: Rudder root server)
- Forced an inventory (cf-agent -KI -Dforce_inventory)
=> Roles are all right now: "Role: Rudder server (rudder-webapp, rudder-inventory-ldap, rudder-jetty, rudder-ldap, rudder-reports, rudder-inventory-endpoint, rudder-db, rudder-server-root)"
This looks fine to me, maybe it can be related to a machine specific issue ?
- Target version changed from 2.11.2 to 2.11.3
- Target version changed from 2.11.3 to 2.11.4
- Target version changed from 2.11.4 to 2.11.5
- Target version changed from 2.11.5 to 2.11.6
- Target version changed from 2.11.6 to 2.11.7
- Target version changed from 2.11.7 to 2.11.8
- Target version changed from 2.11.8 to 2.11.9
- Target version changed from 2.11.9 to 2.11.10
- Status changed from Discussion to Rejected
- Reproduced set to No
I'm rejecting this issue as a duplicate of #6199
Also available in: Atom
PDF
Updated by Nicolas PERRON 
Updated by 
Updated by Matthieu CERDA 
Updated by