Actions
Bug #13662
closedInstalling scale-out-relay should trigger a policy generation
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Very Small
Priority:
91
Name check:
Fix check:
Regression:
Description
i installed the plugin, after an upgrade where policy generation failed because plugin was not there
installing the plugin sloved the issue, but didn't trigger the policy generation - I had to do it myself, which was a bit disapointing
Updated by François ARMAND about 6 years ago
- Assignee set to François ARMAND
We need to set the file that triggers a generation when rudder start during plugin post-hook.
Updated by François ARMAND about 6 years ago
- Effort required set to Very Small
- Priority changed from 80 to 109
Updated by François ARMAND about 6 years ago
- Assignee changed from François ARMAND to Nicolas CHARLES
- Priority changed from 109 to 107
Updated by Nicolas CHARLES almost 6 years ago
- Status changed from New to In progress
Updated by Nicolas CHARLES almost 6 years ago
- Related to User story #14050: Missing flag file to trigger a policy generation added
Updated by Nicolas CHARLES almost 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-plugins/pull/151
- Priority changed from 107 to 104
Updated by Nicolas CHARLES almost 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder:rudder-plugins|a5c2d84ac54ed4ce7e9114e144e831fa1f64dd3d.
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
- Priority changed from 104 to 91
This bug has been fixed in Rudder 5.0-1.2 which was released today.
Actions