Bug #4532
closed
Promises are not generated when Rudder server starts for the first time
Description
The file /opt/rudder/etc/force_technique_reload is somehow not there on the system, hence no technique reloading is done, hence no promises generation
So the server stick with initial policy, until somebody hits the regenerate promises now
Detect on 2.9, likely to be on most version, i'm checking right now
Updated by Jonathan CLARKE about 10 years ago
- Category changed from System techniques to 14
- Status changed from New to 8
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.
Updated by Nicolas CHARLES about 10 years ago
- Target version set to 2.8.3
From 2.8 version, the logs says the file is not there
Updated by Nicolas CHARLES about 10 years ago
- Target version changed from 2.8.3 to 2.6.11
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)
Updated by Nicolas CHARLES about 10 years ago
- Status changed from 8 to Pending technical review
- Assignee set to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/454
Updated by Nicolas CHARLES about 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 96a28a41ab624a8996d23d3e35f5a771234f2cad.
Updated by Anonymous about 10 years ago
Applied in changeset fef045e6f3ef808dc009a6f1bbd17168a416ff1f.
Updated by Vincent MEMBRÉ about 10 years ago
- Subject changed from On a fresh rudder-server-root install, the promises are not generated automaticly to Promises are not generated when Rudder server starts for the first time
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from Pending release to Released
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/
Updated by Benoît PECCATTE about 9 years ago
- Category changed from 14 to Web - Config management