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 about 11 years ago. Updated almost 11 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
 #1

Updated by Nicolas PERRON about 11 years ago

In the first Rudder server the logs /var/log/rudder/weabapp/xxxx.log contains:

[...]
Auto-archive git failure when moving directory (not found in added file): 'groups/xxxxxxxx/xxxxxxxx'. You can safelly ignore that warning if the files was already existing in Git and was not modified by that archive.
[...]

Actions
Copy link
 #2

Updated by Nicolas PERRON about 11 years ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by Jonathan CLARKE about 11 years ago

  • Assignee set to François ARMAND

Francois, can you please investigate and work on this bug? It seems pretty impacting.

Actions
Copy link
 #4

Updated by François ARMAND almost 11 years ago

  • Category set to Web - Config management
  • Status changed from New to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Priority changed from N/A to 2
  • Target version set to 2.6.10
  • Pull Request set to https://github.com/Normation/rudder/pull/414
Actions
Copy link
 #5

Updated by François ARMAND almost 11 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 11 years ago

  • Subject changed from Node Management/Groups screen: The use of sub-categories with the same names will lead to have error when exporting the configuration to another Rudder server to Exporting 2 groups with same name but in different categories to another server Rudder is not working
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ almost 11 years ago

  • Subject changed from Exporting 2 groups with same name but in different categories to another server Rudder is not working to Exporting groups with same name but in different categories to another server Rudder is not working
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ almost 11 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.6.10 which was released today.
Check out:

Actions
Copy link

Also available in: Atom PDF