Bug #11244
closed
Groups are not reloaded after restoring from archive
Added by Benoît PECCATTE over 7 years ago.
Updated about 7 years ago.
Category:
Web - Nodes & inventories
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Description
I found this bug in Rudder version 4.1, on centos7
This bug happens after reloading groups from an archive.
You can reproduce it with the following steps:
- export groups on a server
- import those groups on another server (different machine id ?) via archive menu
- groups are empty
- wait 5mn, groups are still empty
You can workaround this issue by doing likewise:
- click "reload dynamic group" button
- Subject changed from Groups are not reloaded after restoring from arcvhive to Groups are not reloaded after restoring from archive
- Target version set to 3.1.23
- Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Priority changed from 0 to 76
- Assignee set to François ARMAND
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Target version changed from 3.1.23 to 3.1.24
- Status changed from New to In progress
- Priority changed from 76 to 75
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/1754
- Status changed from Pending technical review to Pending release
- Priority changed from 75 to 74
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.24, 4.1.8 and 4.2.1 which were released today.
- Related to Bug #11805: Null pointer exception when restoring group archive. added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by