Bug #2702
closed
After a migration from 2.3.8 to 2.4.0~beta3, the initial-promises of the server are not up to date
Description
After a migration from 2.3.8 to 2.4.0 on Debian Squeeze 64 bits, the initial promises in /var/rudder/cfengine-community/inputs/ are not up to date. A simple copy from /opt/rudder/share/initial-promises can't work since somes variables have to be defined.
A easiest way is to rerun rudder-init.sh but the user shouldn't have to do this action for a migration.
It should be better to copy from /var/rudder/cfengine-community/inputs/ and replaces some variables with the values in LDAP or configuration files.
Updated by Jonathan CLARKE over 11 years ago
- Status changed from New to Discussion
Initial promises should not be restored to the CFEngine inputs directory on an upgrade. Their only purpose is to bootstrap the server, an upgrade by definition means that the server was already running.
However, it could be good to force a promises regeneration after upgrade, maybe via the REST API, so that the promises in effect use the latest system Techniques?
Updated by Nicolas PERRON over 11 years ago
- Status changed from Discussion to New
Updated by Nicolas PERRON over 11 years ago
- Status changed from New to Rejected
Jonathan CLARKE wrote:
Initial promises should not be restored to the CFEngine inputs directory on an upgrade. Their only purpose is to bootstrap the server, an upgrade by definition means that the server was already running.
However, it could be good to force a promises regeneration after upgrade, maybe via the REST API, so that the promises in effect use the latest system Techniques?
I agreed so I rejected this issue.