Actions
Bug #15831
closed
When installing scale out plugin, it doesn't trigger the policy regeneration at the right time
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
I installed scale out plugin in 5.0, and got the following output
Installing /vagrant/plugins/rudder-plugin-scale-out-relay-5.0-1.2-SNAPSHOT.rpkg Successfully triggered a new policy generation [] Restarting jetty $ service rudder-jetty restart Stopping Jetty: OK Setting umask to 0007 Starting Jetty: . . . OK Wed Oct 2 09:53:43 UTC 2019 [root@server log]#
as you can see, it first trigger, then restart - so regeneration takes place when the plugin is not enabled :/
Updated by Nicolas CHARLES about 5 years ago
- Project changed from Rudder to Scale-out relay
- Category deleted (
Plugins integration) - Target version changed from 5.0.14 to 5.0-1.2
Updated by Nicolas CHARLES about 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES about 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-plugins/pull/194
Updated by Nicolas CHARLES about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder:rudder-plugins|66eeb6dfa22eefcb3182b271f8426ece197dffe2.
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0-1.2 which was released today.
Actions