Bug #15687
closed
Bug #10623: Hooks content/permissions are changed during Rudder upgrade (for ex /opt/rudder/etc/hooks.d/policy-generation-node-ready/10-cf-promise-check is replaced)
check if hook-upgrades path exists
Added by Benoît PECCATTE about 5 years ago.
Updated about 5 years ago.
Description
There was a bug in the resolution of #10623
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2066
- Status changed from Pending technical review to Pending release
- Target version changed from 5.0.14 to 5.0.13
- Subject changed from Hooks content/permissions are changed during Rudder upgrade (for ex /opt/rudder/etc/hooks.d/policy-generation-node-ready/10-cf-promise-check is replaced) to check if hook-upgrades path exists
- Name check changed from To do to Reviewed
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.13 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by