Actions
Bug #12712
closed
API generate error 500 when try update a ruleCategory
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:
Very Small
Priority:
0
Name check:
Fix check:
Regression:
Description
when i call https://192.168.1.29/rudder/api/latest/rules/categories/17bd27ad-24db-4b44-8218-ea0ec68714ce on a specific ruleCategory
there is always a error 500 because it is looking for the rootRuleCategory instead
logs:
2018-04-05 22:57:38,706 - rudder-sync - INFO - updateRuleCategory: Kernel 3.x
2018-04-05 22:57:38,715 - rudder-sync - WARNING - apiQuery: eRRoR 500 : POST https://192.168.1.29/rudder/api/latest/rules/categories/17bd27ad-24db-4b44-8218-ea0ec68714ce
2018-04-05 22:57:38,715 - rudder-sync - WARNING - apiQuery: request's answer: {"action":"updateRuleCategory","result":"error","errorDetails":"Could not update Rule category '17bd27ad-24db-4b44-8218-ea0ec68714ce' <- could not find category '17bd27ad-24db-4b44-8218-ea0ec68714ce' in category 'rootRuleCategory'"}
2018-04-05 22:57:38,715 - rudder-sync - WARNING - apiQuery: request's datas: {'parent': 'd552b7df-be18-42f4-be05-c640a33eb168', 'name': 'Kernel 3.x', 'description': ''}
debug: curl -k -H "X-API-Token: token-XXX" -X POST "https://192.168.1.29/rudder/api/latest/rules/categories/17bd27ad-24db-4b44-8218-ea0ec68714ce" -d "{'parent': 'd552b7df-be18-42f4-be05-c640a33eb168', 'name': 'Kernel 3.x', 'description': ''}"
Updated by Benoît PECCATTE almost 6 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 52
Updated by Benoît PECCATTE almost 6 years ago
And if you try to update a category with a depth over 5 you get a 500 too
Updated by Vincent MEMBRÉ almost 6 years ago
- Target version changed from 4.1.13 to 4.1.14
- Priority changed from 52 to 51
Updated by Benoît PECCATTE over 5 years ago
- Target version changed from 4.1.14 to 4.1.15
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.15 to 4.1.16
- Priority changed from 51 to 49
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.16 to 4.1.17
- Priority changed from 49 to 48
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.17 to 4.1.18
- Priority changed from 48 to 0
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.18 to 4.1.19
Updated by Alexis Mousset about 5 years ago
- Target version changed from 4.1.19 to 4.1.20
Updated by François ARMAND about 5 years ago
- Target version changed from 4.1.20 to 4.1.21
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 4.1.21 to 4.1.22
Updated by Vincent MEMBRÉ almost 5 years ago
- Target version changed from 4.1.22 to 4.1.23
Updated by Vincent MEMBRÉ almost 5 years ago
- Target version changed from 4.1.23 to 4.1.24
Updated by Vincent MEMBRÉ almost 5 years ago
- Target version changed from 4.1.24 to 588
Updated by Nicolas CHARLES almost 5 years ago
- Target version changed from 588 to 5.0.13
still the case
Updated by Nicolas CHARLES almost 5 years ago
- Related to Bug #15171: Cannot get Rule tree with the API added
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.13 to 5.0.14
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.14 to 5.0.15
Updated by François ARMAND over 4 years ago
- Effort required set to Very Small
It's most likely simple: build a sub-sub-sub-sub-sub-category, add a rule, see why it breaks.
Updated by Nicolas CHARLES over 4 years ago
- Related to Bug #16164: We cannot get the rules categories with the API added
Updated by Nicolas CHARLES over 4 years ago
This is fixed with https://github.com/Normation/rudder/pull/2587
marking this ticket as a duplicate of #16164
Updated by Nicolas CHARLES over 4 years ago
- Status changed from New to Rejected
Actions