Project

General

Profile

Actions

Bug #10216

closed

"id" setting is silently ignored for new group created through the REST API.

Added by Dmitry Svyatogorov about 4 years ago. Updated 8 months ago.

Status:
Released
Priority:
N/A
Category:
API
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
88
Tags:

Description

According to https://www.rudder-project.org/rudder-api-doc/#api-Groups-createGroup
new group can be created with the exact "id". But as for Rudder 4.0.2, "id" setting is silently ignored and new UUID is generated.
For example try to PUT the following json:
{
  "id": "9a92538b-d01f-4157-9fff-ed1d1a8d3443",
  "category": "GroupRoot",
  "enabled": true,
  "displayName": "###TEST#",
  "query": {
    "select": "node",
    "composition": "And",
    "where": [
      {
        "objectType": "node",
        "attribute": "nodeHostname",
        "comparator": "regex",
        "value": ".*\\.xxx\\.tld" 
      }
    ]
  }
}
  • The answer looks like
    {"action": "createGroup","id": "2ef61fa0-426d-40a1-99c1-c1f62b4d5664","result": "success"…
    

    Then check the "id" in answer body / WEB-UI against the requested value.

This seriously complicates group & rule transmitting between 2 nodes through REST-API because of need in translation dictionary.

Actions #1

Updated by Vincent MEMBRÉ about 4 years ago

  • Assignee set to Vincent MEMBRÉ
  • Target version set to 3.1.18

Thus bug was fixed on Directive on a recent version, but we did not took time to look in other versions

Actions #2

Updated by Dmitry Svyatogorov about 4 years ago

Sorry, Vincent. What version is "recent"? "Latest release: 4.0.2" is affected (I found the problem affects at least Groups and Rules PUT API).
Upcoming 4.0.3? It's really important for me as it can significantly reduce my current task.

Actions #3

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #4

Updated by Benoît PECCATTE about 4 years ago

  • Found in version (s) 4.0.2 added
Actions #5

Updated by Benoît PECCATTE about 4 years ago

  • Found in version(s) old deleted (4.0.2)
Actions #6

Updated by François ARMAND about 4 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
Actions #7

Updated by Benoît PECCATTE about 4 years ago

  • Priority set to 36
Actions #8

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #9

Updated by Jonathan CLARKE about 4 years ago

  • Assignee deleted (Vincent MEMBRÉ)
  • Priority changed from 36 to 35
Actions #10

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #11

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.21 to 3.1.22
  • Priority changed from 35 to 34
Actions #12

Updated by Benoît PECCATTE almost 4 years ago

  • Priority changed from 34 to 49
Actions #13

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.22 to 3.1.23
  • Priority changed from 49 to 48
Actions #14

Updated by Dmitry Svyatogorov over 3 years ago

As for current Rudder 4.1.5, uuid is ignored in creation of all objects except of directives (and parameters, as they are passed by name).

  • Those techniques which are constructed from NCF are in fact out-of-API. The workaround is to transfer ncf tree to new server, then save each technique through web-ui.
    After that, ncf becomes available in directives.
Actions #15

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.23 to 3.1.24
  • Priority changed from 48 to 47
Actions #16

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.24 to 3.1.25
  • Priority changed from 47 to 46
Actions #17

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.25 to 387
  • Priority changed from 46 to 45
Actions #18

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 387 to 4.1.10
  • Priority changed from 45 to 44
Actions #19

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 4.1.10 to 4.1.11
  • Priority changed from 44 to 43
Actions #20

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 4.1.11 to 4.1.12
Actions #21

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions #22

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions #23

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions #24

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions #25

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions #26

Updated by François ARMAND over 2 years ago

  • Priority changed from 43 to 0

it's still the case in 4.3.7.

Actions #27

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.1.17 to 4.1.18
Actions #28

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.1.18 to 4.1.19
Actions #29

Updated by Alexis MOUSSET over 2 years ago

  • Target version changed from 4.1.19 to 4.1.20
Actions #30

Updated by François ARMAND about 2 years ago

  • Target version changed from 4.1.20 to 4.1.21
Actions #31

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 4.1.21 to 4.1.22
Actions #32

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 4.1.22 to 4.1.23
Actions #33

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 4.1.23 to 4.1.24
Actions #34

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 4.1.24 to 588
Actions #35

Updated by François ARMAND almost 2 years ago

  • Target version changed from 588 to 5.0.13
  • User visibility changed from Operational - other Techniques | Technique editor | Rudder settings to Operational - other Techniques | Rudder settings | Plugins
  • Effort required set to Small
  • Priority changed from 0 to 56

We need to accept creation of object with a predefined ID, else we won't be able to synchronise things between rudder instances by API.
We need to check that the ID is not already present and fail on that case.

Actions #36

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 5.0.13 to 5.0.14
Actions #37

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 5.0.14 to 5.0.15
Actions #38

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 5.0.15 to 5.0.16
Actions #39

Updated by Alexis MOUSSET about 1 year ago

  • Target version changed from 5.0.16 to 5.0.17
Actions #40

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 5.0.17 to 5.0.18
  • Priority changed from 56 to 57
Actions #41

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 5.0.18 to 5.0.19
  • Priority changed from 57 to 59
Actions #42

Updated by François ARMAND 9 months ago

  • Tags set to Sponsored
  • Priority changed from 59 to 88
Actions #43

Updated by François ARMAND 9 months ago

  • Assignee set to Elaad FURREEDAN
Actions #44

Updated by Elaad FURREEDAN 9 months ago

  • Status changed from New to In progress
Actions #45

Updated by Elaad FURREEDAN 9 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Elaad FURREEDAN to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/3194
Actions #46

Updated by Anonymous 9 months ago

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

Updated by Vincent MEMBRÉ 8 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.19, 6.0.8 and 6.1.4 which were released today.

Actions

Also available in: Atom PDF