Bug #5280: When the ldap tree changes, Rudder can't always access new info after an update - Rudder - Issue Tracker

Actions

Copy link

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.

Status:

Rejected

Priority:

Assignee:

Nicolas CHARLES

Category:

System integration

Target version:

2.11.10

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

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

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.11.1 to 2.11.2

Actions

Copy link

Updated by Nicolas CHARLES over 10 years ago

Assignee set to Matthieu CERDA

Running /etc/init.d/rudder-slapd reindex solves the issue

Actions

Copy link

Updated by Matthieu CERDA over 10 years ago

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 ?

Actions

Copy link