Project

General

Profile

Actions

Bug #5439

closed

Upgrade from 2.10.x to 2.10.5 can prevent promises generation

Added by Nicolas CHARLES over 9 years ago. Updated over 8 years ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When we upgrade from 2.10.x to 2.10.5 using the standard procedure, we are in a state where promise generation is impossible.

We introduced new generic methods in ncf that are not compatible with Rudder 2.10, and we also included a script ( see http://www.rudder-project.org/redmine/issues/5402 ) to load only the relevant Techniques.
However the promises that already exist on the Policy Server don't use yet this script, so they cannot avoid loading the bad generic methods.

The specific upgrade procedure would be:

With Debian like system:

apt-get install rudder-server-root
/etc/init.d/rudder-jetty restart
# Wait for the Web Interface to be fully started
# Click on Update on the top right hand side corner, to trigger promises regeneration
apt-get install ncf

With RPM based system

yum update "rudder-*" 
/etc/init.d/rudder-jetty restart
# Wait for the Web Interface to be fully started
# Click on Update on the top right hand side corner, to trigger promises regeneration
yum update ncf

If you updated both rudder-server-root and ncf at the same time, and are stuck, you can resolv the issue by running the command

cp /opt/rudder/share/tools/list-compatible-inputs  /var/rudder/tools/

and there regenerate promises (in the Web Interface, click on "Update" on the top right hand side corner)


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #5402: Agent can't run because some ncf promises are CFEngine 3.6 specificReleasedJonathan CLARKE2014-08-19Actions
Actions

Also available in: Atom PDF