Project

General

Profile

Actions
Copy link

Bug #4149

closed

Exporting groups with same name but in different categories to another server Rudder is not working

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

Status:
Released
Priority:
2
Assignee:
Nicolas CHARLES
Category:
Web - Config management
Target version:
2.6.10
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

In the Node Management/Groups screen, if several Sub-categories have the same name, it will lead to an error when the Rudder Server configuration will be exported to another one.

For example:

Debian
|--Servers
|  -- Group A containing debian01.local.lan
 --Clients
   -- Group B containing debian11.local.lan
SLES
|--Servers
|  -- Group C containing sles01.local.lan
 --Clients
   -- Group D containing sles11.local.lan

After an export, on the other Rudder Server, the Groups C and D will not be present, any Rule depending on these Groups will display an Error and a message error will be in the /var/log/webapp/xxxxx.log:

[...]Ignoring Active Categor with ID 'yyyyyyyyyyyyy' because its name is 'Servers'  already referenced by category with ID 'xxxxxxxxxx'[...]

A workaround is to create another SubCategories, move the groups to them and then reexport.

Actions
Copy link

Also available in: Atom PDF