Actions
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.
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
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.2.1 to 3.2.2
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.2.2 to 3.2.3
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.2.3 to 3.2.4
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.2.4 to 3.2.5
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.2.5 to 3.2.6
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.2.6 to 3.2.7
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.2.7 to 3.2.8
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.2.8 to 3.2.9
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.2.9 to 3.2.10
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.2.10 to 3.2.11
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.2.11 to 339
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 339 to 4.0.4
Updated by Jonathan CLARKE over 7 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
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.0.4 to 4.0.5
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.0.5 to 4.0.6
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.0.6 to 4.0.7
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.0.7 to 357
Updated by Alexis Mousset over 7 years ago
- Target version changed from 357 to 4.1.6
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.6 to 4.1.7
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.7 to 4.1.8
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.8 to 4.1.9
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.9 to 4.1.10
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.10 to 4.1.11
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.11 to 4.1.12
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.12 to 4.1.13
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.13 to 4.1.14
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.1.14 to 4.1.15
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.15 to 4.1.16
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.16 to 4.1.17
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