Bug #7301
closed
promises are not regenerated when a node is transformed into a relay
Added by Vincent MEMBRÉ about 9 years ago.
Updated almost 9 years ago.
Category:
Server components
Description
After calling rudder-node-to-relay promises are note generated straight away, we should trigger a policy reload from api at the end of the script
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to Matt Ungaro
- Pull Request set to https://github.com/Normation/rudder-packages/pull/766
- Assignee changed from Matt Ungaro to Benoît PECCATTE
Why not use http://localhost:8080/ directly?
You could make sure you hit the rudder API...
I am just asking because we for example modified rudder's vhost config to listen on https only on a dedicated Service IP instead of *:443, as there are also other services running on https on that host...
- Target version changed from 2.10.19 to 2.10.20
- Status changed from Pending technical review to Discussion
- Assignee changed from Benoît PECCATTE to Vincent MEMBRÉ
- Status changed from Discussion to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.10.20, 2.11.17, 3.0.12 and 3.1.5 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by