Project

General

Profile

Actions

Bug #9087

closed

Error on promises generation when there are no properties files

Added by Nicolas CHARLES over 7 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
System techniques
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Small
Priority:
47
Name check:
Fix check:
Regression:

Description

If there are no properties defined, we have the following error at generation:

Command to check generated promises is: '/var/rudder/cfengine-community/bin/cf-promises -f /var/rudder/cfengine-community/inputs.new/promises.cf'
⇨ error: readjson: data error parsing JSON file 'cf_null': No data
⇨ error: readjson: data error parsing JSON file 'cf_null': No data
⇨ error: readjson: data error parsing JSON file 'cf_null': No data

issue is we don't check that there are any files in the findfiles in common/1.0/properties.cf - if folder is empty, then it returns cf_null
This is pretty impacting as when doing update of Rudder, we come from a state with no properties to a state with properties, but we check the previous generated properties (${sys.workdir}/inputs/properties.d/*.json)


Related issues 3 (0 open3 closed)

Related to Rudder - Bug #8756: Expose node properties in properties.d not propertiesReleasedNicolas CHARLES2016-07-26Actions
Related to Rudder - User story #8737: Expose node properties as a global CFEngine data variableReleasedNicolas CHARLES2016-07-26Actions
Has duplicate Rudder - Bug #9106: If properties.d doesn't exists, cf-promises fails with an "error 'cf_null'"Rejected2016-09-22Actions
Actions #1

Updated by Nicolas CHARLES over 7 years ago

  • Related to Bug #8756: Expose node properties in properties.d not properties added
Actions #2

Updated by Nicolas CHARLES over 7 years ago

  • Related to User story #8737: Expose node properties as a global CFEngine data variable added
Actions #3

Updated by Nicolas CHARLES over 7 years ago

  • How to reproduce updated (diff)
Actions #4

Updated by Nicolas CHARLES over 7 years ago

  • Related to Bug #9106: If properties.d doesn't exists, cf-promises fails with an "error 'cf_null'" added
Actions #5

Updated by François ARMAND over 7 years ago

  • Related to deleted (Bug #9106: If properties.d doesn't exists, cf-promises fails with an "error 'cf_null'")
Actions #6

Updated by François ARMAND over 7 years ago

  • Has duplicate Bug #9106: If properties.d doesn't exists, cf-promises fails with an "error 'cf_null'" added
Actions #7

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #8

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #9

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #10

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #11

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #12

Updated by Benoît PECCATTE about 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
Actions #13

Updated by François ARMAND about 7 years ago

  • User visibility changed from Operational - other Techniques | Technique editor | Rudder settings to Infrequent - complex configurations | third party integrations
  • Effort required set to Small
Actions #14

Updated by Benoît PECCATTE about 7 years ago

  • Priority set to 31
Actions #15

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #16

Updated by Jonathan CLARKE almost 7 years ago

  • Priority changed from 31 to 30
Actions #17

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #18

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #19

Updated by Benoît PECCATTE almost 7 years ago

  • Priority changed from 30 to 39
Actions #20

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.22 to 3.1.23
  • Priority changed from 39 to 38
Actions #21

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.23 to 3.1.24
  • Priority changed from 38 to 37
Actions #22

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #23

Updated by Benoît PECCATTE over 6 years ago

  • Priority changed from 37 to 47
Actions #24

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.25 to 387
Actions #25

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 387 to 4.1.10
Actions #26

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.10 to 4.1.11
Actions #27

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
Actions #28

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions #29

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions #30

Updated by Benoît PECCATTE over 5 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions #31

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions #32

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions #33

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF