Project

General

Profile

Actions

Bug #2403

closed

Groups : "Can not find node 1ba2993b-af48-4317-9231-a69d3049c540"

Added by Francois BAYART about 12 years ago. Updated about 12 years ago.

Status:
Released
Priority:
1
Category:
Web - Nodes & inventories
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I have created a new category group and I have added a group in this category.
This group was named "test", after I have created it I would like to change it to "root" category.

A warning message in red appear, but il was not clear so I click to "Search nodes" and "Groups" to refresh the page and now I have this beautiful message "Can not find node 1ba2993b-af48-4317-9231-a69d3049c540".


Files

Can_not_find_node.png (34.1 KB) Can_not_find_node.png Environment : Debian Squeeze, rudder by official repository release 2.3.6~ Francois BAYART, 2012-04-02 16:49
ldap_dump.txt (5.46 KB) ldap_dump.txt Francois BAYART, 2012-04-03 10:53
var-log-rudder-webapp.zip (6.8 KB) var-log-rudder-webapp.zip Francois BAYART, 2012-04-03 10:53

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #2223: The default group query is incompleteReleased2012-01-31Actions
Actions #1

Updated by François ARMAND about 12 years ago

So it seems that the move of "test" group was somehow corrupted, and that the group was not correctly deleted from the Louvain-la-Neuve category (and not created at all in root). So the category only keep an id (the beautiful UUID you are seeing), but the matching group is nowhere to be found.

That's a BIG bug. Of course, for now I can't reproduce it. So have you any more information about what happened/how it happened:

  • do you remember what was the error message ? (side note: if it wasn't clear, we have to improve it!)
  • you tried to move the group with a drag'n'drop ?
  • do have anything in Rudder logs that could lead to understand what happened ?
  • could you attach a dump of Rudder LDAP Inventory outputed by that command (change relevant user/host/etc parts):
/opt/rudder/bin/ldapsearch -D "cn=manager,cn=rudder-configuration" -w secret -p 389 -h localhost -b "groupCategoryId=GroupRoot,ou=Rudder,cn=rudder-configuration"

Thanks,

Updated by Francois BAYART about 12 years ago

That's a BIG bug. Of course, for now I can't reproduce it. So have you any more information about what happened/how it happened:

  • do you remember what was the error message ? (side note: if it wasn't clear, we have to improve it!)

I have reproduce the problem without problem, so I have this error if I try to create a new group named "mongroupe1"
-----snip here-----
The form contains some errors, please correct them
An error occurred while updating the group: Error when updating the group NodeGroupId(2148e0b1-e216-4aff-a176-bae3e590da2c)
-----snip here-----

  • you tried to move the group with a drag'n'drop ?

No by the select menu.

  • do have anything in Rudder logs that could lead to understand what happened ?

I don't know, you can find the /var/log/rudder/webapp in attachment.

  • could you attach a dump of Rudder LDAP Inventory outputed by that command (change relevant user/host/etc parts):

attachment

Actions #3

Updated by François ARMAND about 12 years ago

  • Status changed from New to 8
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Priority changed from N/A to 1
  • Target version set to 2.3.7

OK, so the log show the following error:

10:32:51.440 [qtp429405933-70] ERROR c.n.r.web.components.NodeGroupForm - An error occurred while updating the group:Error when updating the group NodeGroupId(2148e0b1-e216-4aff-a176-bae3e590da2c) 

<- Error when mapping change record to a diff object: LDIFModifyChangeRecord(dn='nodeGroupId=2148e0b1-e216-4aff-a176-bae3e590da2c,groupCategoryId=43f06347-9b84-4321-8f10-3b250cb6cb78,groupCategoryId=GroupRoot,ou=Rudder,cn=rudder-configuration', mods={LDAPModification(type=replace, attr=description, values={'ceci est un groupe1'}), LDAPModification(type=replace, attr=jsonNodeGroupQuery, values={'{"select":"node","composition":"And","where":[{"objectType":"node","attribute":"OS","comparator":"eq","value":""}]}'})})

<- Missing required value for comparator 'eq' in line 'StringCriterionLine(node,OS,eq,None)'

That leads to bug #2223 that wasn't identified in branch 2.3.

NicoC, could you please backport the fixe ?

Actions #4

Updated by François ARMAND about 12 years ago

  • Assignee changed from Nicolas CHARLES to François ARMAND
Actions #5

Updated by François ARMAND about 12 years ago

  • Status changed from 8 to Pending technical review

Backported commit e254671f to fix the problem on 2.3 branch.

Actions #6

Updated by Nicolas CHARLES about 12 years ago

  • Status changed from Pending technical review to Released
  • % Done changed from 0 to 100

This looks correct, thank you both Francois

Actions

Also available in: Atom PDF