Actions
Bug #17081
closed
Agent 6.0 can't update policies from Rudder 5.0
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
Related to #16576.
Here, the problem seems to be that generation is not able to find the cfengine key even if present:
[2020-04-08 12:06:22] INFO policy.generation - Node 'agent.rudder.local' (ce6cd53a-ee9b-4c95-aff4-6277809e40e1) has an unsuported key type (CFEngine agent with certificate?) and a we do not know how to generate a hash yet
Updated by François ARMAND about 4 years ago
- Status changed from New to In progress
Updated by François ARMAND about 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/2878
Updated by François ARMAND about 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|7af90273cd81e5340da548d99595e2a0b00d0f2c.
Updated by Alexis Mousset about 4 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset about 4 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ about 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.17 and 6.0.5 which were released today.
Actions