Bug #5439
Updated by Nicolas CHARLES over 9 years ago
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: h2. With Debian like system: <pre> apt-get install rudder-server-root /etc/init.d/rudder-jetty restart # Wait 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 </pre> h2. With RPM based system <pre> yum update "rudder-*" /etc/init.d/rudder-jetty restart # Wait 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 </pre> 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 <pre> cp /opt/rudder/share/tools/list-compatible-inputs /var/rudder/tools/ </pre> and there regenerate promises (in the Web Interface, click on "Update" on the top right hand side corner)