Rudder

After upgrade from 6.2.0 -> 6.2.1, all plugins are disabled.

root@orchestrateur-4:~# rudder package list
+-------------------------------------+----------+----------------+----------+
| Plugin Name                         | Version  | Latest release | Status   |
+-------------------------------------+----------+----------------+----------+
| rudder-plugin-reporting             | 6.2-1.5  | 6.2-1.5        | disabled |
| rudder-plugin-cve                   | 6.2-1.4  | 6.2-1.4        | disabled |
| rudder-plugin-change-validation     | 6.2-1.10 | 6.2-1.10       | disabled |
| rudder-plugin-notify                | 6.2-1.2  | 6.2-1.2        | enabled  |
| rudder-plugin-node-external-reports | 6.2-1.9  | 6.2-1.9        | disabled |
| rudder-plugin-datasources           | 6.2-1.11 | 6.2-1.11       | disabled |
| rudder-plugin-user-management       | 6.2-1.8  | 6.2-1.8        | disabled |
| rudder-plugin-solaris               | 6.2-1.2  | 6.2-1.2        | disabled |

and before upgrade rudder package list was :

+-------------------------------------+----------+----------------+---------+
| Plugin Name                         | Version  | Latest release | Status  |
+-------------------------------------+----------+----------------+---------+
| rudder-plugin-reporting             | 6.2-1.5  | 6.2-1.5        | enabled |
| rudder-plugin-cve                   | 6.2-1.4  | 6.2-1.4        | enabled |
| rudder-plugin-change-validation     | 6.2-1.10 | 6.2-1.10       | enabled |
| rudder-plugin-notify                | 6.2-1.2  | 6.2-1.2        | enabled |
| rudder-plugin-node-external-reports | 6.2-1.9  | 6.2-1.9        | enabled |
| rudder-plugin-datasources           | 6.2-1.11 | 6.2-1.11       | enabled |
| rudder-plugin-user-management       | 6.2-1.8  | 6.2-1.8        | enabled |
| rudder-plugin-solaris               | 6.2-1.2  | 6.2-1.2        | enabled |

This happens because /opt/rudder/share/webapps/rudder.xml is replaced when rudder-webapp packages are extracted in /opt/rudder/share/webapps.

Running "rudder package plugin restore-status" should be called at some moment to reenable plugin. I think right before check-compatibility call is the good time!