Actions
Bug #3548
closed
Regenerate now make pending rule change request invalid
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When you create a change request on a rule, and then regenerate (deploy), the change request can not be merged ("warning, the rule changed since CR creation, decline only, etc") .
That at least happen to change request with an error, and it's likelly to be the "serial" of the rule that changed, but clearly it should not be taken into account here.
Updated by François ARMAND over 11 years ago
- Pull Request set to https://github.com/Normation/rudder/pull/196
Updated by François ARMAND over 11 years ago
- Status changed from In progress to Rejected
- Assignee changed from François ARMAND to Vincent MEMBRÉ
Updated by Matthieu CERDA over 11 years ago
- Target version changed from 2.6.0~rc1 to 2.6.0
Updated by François ARMAND over 11 years ago
- Status changed from Rejected to Released
Updated by François ARMAND over 11 years ago
- Target version changed from 2.6.0 to 2.6.0~rc1
Actions