Project

General

Profile

Actions
Copy link

Bug #8221

closed

Promises are not regenerated after changing group name, preventing usage of classes

Bug #8221: Promises are not regenerated after changing group name, preventing usage of classes

Added by Vincent MEMBRÉ over 9 years ago. Updated over 3 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
François ARMAND
Category:
Web - Config management
Target version:
3.2.3
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Since we added clases depending on group, we should update the generated promises when we change group name so the classes are updated and use the new name of the group.

Triggering a clear cache fix this issue

Related issues 1 (0 open — 1 closed)

Related to Rudder - User story #7424: Add cfengine classes for each group of a nodeReleasedNicolas CHARLESActions

Updated by Vincent MEMBRÉ over 9 years ago Actions
Copy link
 #1

  • Status changed from New to In progress

Updated by Jonathan CLARKE over 9 years ago Actions
Copy link
 #2

  • Related to User story #7424: Add cfengine classes for each group of a node added

Updated by Vincent MEMBRÉ over 9 years ago Actions
Copy link
 #3

  • 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/1081

Updated by Vincent MEMBRÉ over 9 years ago Actions
Copy link
 #4

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

Updated by Vincent MEMBRÉ over 9 years ago Actions
Copy link
 #5

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.2.3 which was released on 2016-06-01, but not announced.

Updated by Alexis Mousset over 3 years ago Actions
Copy link
 #6

  • Priority set to 0
Actions
Copy link

Also available in: PDF Atom