New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #17570: Trigger promises generation when promoting a node to relay #307
Conversation
Commit modified |
02344f4
to
9ca42cb
Compare
Are you sure it needs a reload ? i don't think because rule creation already reloads |
I don't see where the reload is performed, no eventlog indicates this and it seems that in https://github.com/Normation/rudder/blob/master/webapp/sources/rudder/rudder-core/src/main/scala/com/normation/rudder/repository/ldap/LDAPRuleRepository.scala#L186 there is no reload at this point |
@@ -59,6 +61,7 @@ class ScaleOutRelayService( | |||
} else { | |||
nodeInfos.succeed | |||
} | |||
_ <- clearCacheService.clearNodeConfigurationCache(storeEvent = true, actor) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In fact you should trigger a deployment not delete the whole configurationCache.
We used to call deploy api that only starts a deployment:
asyncDeploymentAgent ! AutomaticStartDeployment(modId, actor)
with
, asyncDeploymentAgent : AsyncDeploymentActor
you can put it in the yield section
9ca42cb
to
8aa4f46
Compare
Commit modified |
OK, merging this PR |
https://issues.rudder.io/issues/17570