Project

General

Profile

Actions

Bug #12209

closed

metadata.xml not generated when saving a technique from editor

Added by François ARMAND about 6 years ago. Updated about 6 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Technique editor
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
76
Name check:
Fix check:
Regression:

Description

When saving a technique in editor, we have a success message but the metadata.xml is not correctly generated, and so the technique is not available in directive list afterward.

If we look in js debug console, we can see:

Request URL: https://192.168.49.2/rudder/secure/api/ncf
Request Method: POST
Status Code: 500 Server Error
Remote Address: 192.168.49.2:443
Referrer Policy: no-referrer-when-downgrade

{
  "action": "updateTechnique",
  "result": "error",
  "errorDetails": "Authorization error: User 'admin' is not allowed to access POST secure/api/ncf" 
}

There is two problems here: we don't get the error in technique editor (we have success but actually it's not the case). This one is managed in ticket: #12210

And we get an error 500 preventing metadata to be created (that ticket).

Actions #1

Updated by François ARMAND about 6 years ago

  • Description updated (diff)
Actions #2

Updated by François ARMAND about 6 years ago

  • Status changed from New to In progress
Actions #3

Updated by François ARMAND about 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1870
Actions #4

Updated by Rudder Quality Assistant about 6 years ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND
Actions #5

Updated by François ARMAND about 6 years ago

  • Status changed from Pending technical review to Pending release
Actions #6

Updated by Vincent MEMBRÉ about 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.3.0~rc1 which was released today.

Actions

Also available in: Atom PDF