Actions
Bug #10578
closedCannot add node property when audit message is mandatory
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
36
Name check:
Fix check:
Regression:
Description
Hi,
When "Make message mandatory" is set in the global configuration, I cannot add a property to a node.
I get the following error:
An error occured while saving this new property : An error occured while updating Node '6cf42768-b982-4edf-a2d1-d1f418446ede' <- Reason field is mandatory and should be at least 5 characters long
No issue when "Make message mandatory" is not set.
Updated by Alexis Mousset over 7 years ago
- Category set to Web - Config management
- Target version set to 4.1.1
Updated by Rémi Verchère over 7 years ago
FYI, same behaviour/error when I try to modify the policy mode for a node, but withour explanations.
1. On the web page:
"Error during saving changes"
2. On the log file:
[2017-04-10 18:56:19] ERROR com.normation.rudder.web.rest.node.NodeAPI5 - An error occured while updating Node '926f938f-fdd0-4375-a6a6-dc78b970adaa' <- Reason field is mandatory and should be at least 5 characters long [2017-04-10 18:56:19] ERROR com.normation.rudder.web.rest.RestUtils - "An error occured while updating Node '926f938f-fdd0-4375-a6a6-dc78b970adaa' <- Reason field is mandatory and should be at least 5 characters long"
Updated by Jonathan CLARKE over 7 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Priority changed from 0 to 36
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/1627
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|220b17956f6c8f2e9ee0e6577ecaff7ff0e022d3.
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.1 which was released today.
- 4.1.1: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by François ARMAND over 7 years ago
- Related to Bug #10669: Cannot switch Agent Policy Mode on Node Settings page added
Updated by François ARMAND over 7 years ago
- Related to deleted (Bug #10669: Cannot switch Agent Policy Mode on Node Settings page)
Updated by François ARMAND over 7 years ago
- Has duplicate Bug #10669: Cannot switch Agent Policy Mode on Node Settings page added
Updated by François ARMAND almost 3 years ago
- Related to Architecture #10637: Change message must be configurable for policy mode/property change added
Actions