Actions
Bug #20926
closed
Starting policy generation by hand fails if node-configuration-hashes.json
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:
To do
Fix check:
Checked
Regression:
Description
You get the generation pop-up and it just don't close with nothing happening.
To reproduce: delete file `/var/rudder/policy-generation-info/node-configuration-hashes.json`, try to start a policy generation with `regenerate all policies` button in rudder top right ui
WORKAROUND :
On root, each time a generation fails, do:
touch /var/rudder/policy-generation-info/node-configuration-hashes.json
Updated by François ARMAND almost 3 years ago
- Status changed from New to In progress
Updated by François ARMAND almost 3 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/4215
Updated by François ARMAND almost 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|b823f81ff06d9ffff0c6c688cad707c869067cc5.
Updated by Nicolas CHARLES over 2 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.2.13, 7.0.2 and 7.1.0~rc1 which were released today.
Actions