Project

General

Profile

Actions
Copy link

Bug #7853

closed

If a node has a cfengine community + cfengine nova agent, the generation fails

Added by Nicolas CHARLES almost 9 years ago. Updated about 6 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
4.1.17
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
54
Name check:
Fix check:
Regression:

Description

When both agent are present on a node, the generation fails as it does not find the generated promises (most probably, the promises are moved at the wrong level/time)
Exists on 3.2, may be on other platforms

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.2.1 to 3.2.2
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.2.2 to 3.2.3
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.2.3 to 3.2.4
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.2.4 to 3.2.5
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.2.5 to 3.2.6
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.2.6 to 3.2.7
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.2.7 to 3.2.8
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.2.8 to 3.2.9
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.2.9 to 3.2.10
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.2.10 to 3.2.11
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.2.11 to 339
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 339 to 4.0.4
Actions
Copy link
 #13

Updated by Jonathan CLARKE almost 8 years ago

  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
  • User visibility set to Infrequent - complex configurations | third party integrations
Actions
Copy link
 #14

Updated by Benoît PECCATTE over 7 years ago

  • Priority set to 41
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.0.4 to 4.0.5
Actions
Copy link
 #16

Updated by Jonathan CLARKE over 7 years ago

  • Assignee deleted (François ARMAND)
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.0.5 to 4.0.6
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.0.6 to 4.0.7
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.0.7 to 357
Actions
Copy link
 #20

Updated by Benoît PECCATTE over 7 years ago

  • Priority changed from 41 to 54
Actions
Copy link
 #21

Updated by Alexis Mousset over 7 years ago

  • Target version changed from 357 to 4.1.6
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.6 to 4.1.7
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.7 to 4.1.8
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.8 to 4.1.9
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.9 to 4.1.10
Actions
Copy link
 #26

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.10 to 4.1.11
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
Actions
Copy link
 #28

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions
Copy link
 #29

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions
Copy link
 #30

Updated by Benoît PECCATTE over 6 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions
Copy link
 #31

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions
Copy link
 #32

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions
Copy link
 #33

Updated by François ARMAND about 6 years ago

  • Status changed from New to Rejected

This was correct on 4.1 when working on nova integration.
Please reopen it if the bug appear again.

Actions
Copy link

Also available in: Atom PDF