Project

General

Profile

Bug #10216

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

Added by Dmitry Svyatogorov over 3 years ago. Updated 9 days 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.

#1

Updated by Vincent MEMBRÉ over 3 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

#2

Updated by Dmitry Svyatogorov over 3 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.

#3

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.18 to 3.1.19
#4

Updated by Benoît PECCATTE over 3 years ago

  • Found in version (s) 4.0.2 added
#5

Updated by Benoît PECCATTE over 3 years ago

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

Updated by François ARMAND over 3 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
#7

Updated by Benoît PECCATTE over 3 years ago

  • Priority set to 36
#8

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.19 to 3.1.20
#9

Updated by Jonathan CLARKE over 3 years ago

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

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.20 to 3.1.21
#11

Updated by Vincent MEMBRÉ over 3 years ago

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

Updated by Benoît PECCATTE about 3 years ago

  • Priority changed from 34 to 49
#13

Updated by Vincent MEMBRÉ about 3 years ago

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

Updated by Dmitry Svyatogorov about 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.
#15

Updated by Vincent MEMBRÉ about 3 years ago

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

Updated by Vincent MEMBRÉ almost 3 years ago

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

Updated by Vincent MEMBRÉ almost 3 years ago

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

Updated by Vincent MEMBRÉ almost 3 years ago

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

Updated by Vincent MEMBRÉ over 2 years ago

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

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.1.11 to 4.1.12
#21

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.1.12 to 4.1.13
#22

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 4.1.13 to 4.1.14
#23

Updated by Benoît PECCATTE about 2 years ago

  • Target version changed from 4.1.14 to 4.1.15
#24

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 4.1.15 to 4.1.16
#25

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 4.1.16 to 4.1.17
#26

Updated by François ARMAND almost 2 years ago

  • Priority changed from 43 to 0

it's still the case in 4.3.7.

#27

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 4.1.17 to 4.1.18
#28

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.1.18 to 4.1.19
#29

Updated by Alexis MOUSSET over 1 year ago

  • Target version changed from 4.1.19 to 4.1.20
#30

Updated by François ARMAND over 1 year ago

  • Target version changed from 4.1.20 to 4.1.21
#31

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.1.21 to 4.1.22
#32

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.1.22 to 4.1.23
#33

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.1.23 to 4.1.24
#34

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 4.1.24 to 588
#35

Updated by François ARMAND about 1 year 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.

#36

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 5.0.13 to 5.0.14
#37

Updated by Vincent MEMBRÉ 12 months ago

  • Target version changed from 5.0.14 to 5.0.15
#38

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 5.0.15 to 5.0.16
#39

Updated by Alexis MOUSSET 7 months ago

  • Target version changed from 5.0.16 to 5.0.17
#40

Updated by Vincent MEMBRÉ 5 months ago

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

Updated by Vincent MEMBRÉ 2 months ago

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

Updated by François ARMAND about 1 month ago

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

Updated by François ARMAND about 1 month ago

  • Assignee set to Elaad FURREEDAN
#44

Updated by Elaad FURREEDAN 30 days ago

  • Status changed from New to In progress
#45

Updated by Elaad FURREEDAN 29 days 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
#46

Updated by Anonymous 29 days ago

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

Updated by Vincent MEMBRÉ 9 days 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.

Also available in: Atom PDF