Rudder

After a quick investigation, touching the /opt/rudder/etc/force_technique_reload file, then restarting jetty shows this in the logs:

[2014-02-26 16:56:26] INFO  bootstrap.liftweb.checks.CheckTechniqueLibraryReload - Flag file '/opt/rudder/etc/force_technique_reload' found, reload Technique library now
[2014-02-26 16:56:26] INFO  bootstrap.liftweb.checks.CheckTechniqueLibraryReload - Successfully reloaded Technique library on start up. now deleting flag file '/opt/rudder/etc/force_technique_reload'
[2014-02-26 16:56:27] INFO  bootstrap.liftweb.checks.CheckTechniqueLibraryReload - Flag file '/opt/rudder/etc/force_technique_reload' successfully removed

So that mechanism seems to work.

However, I recall that a recent change in #4479 made us no longer run a promise generation after an export. And the export is run on first start. So this "used to work" by magic, but no longer does...

I guess the underlying bug is that the initial technique library loading doesn't call a promise generation. It should.

From 2.8 version, the logs says the file is not there

Ha. So when the application starts, it detects that not git version is stored, so it initialize it with latest version. Then the flag is read, and Rudder checks the git. It is obviously the same, so nothing to do.
Hence the problem.

If we initialize the git revision, we should trigger a redeploy (we have no mean to know if the state is the same as before)

Applied in changeset 96a28a41ab624a8996d23d3e35f5a771234f2cad.

This bug has been fixed in Rudder 2.6.11, which was released today.
Check out:

• The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-March/000077.html
• The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog26
• Download information: https://www.rudder-project.org/site/get-rudder/downloads/