Rudder

Yes, it was designed to use a database on the local machine...

We should make it possible to use a remote postgresql.

For context: this is related to running the Rudder server components on separate servers, see #4654.

What appears to be happening here is simple: the rudder-reports package is being installed. The role of this package is... to set up the database :) Therefore, what should happen, is, very simple, that the dependency from rudder-webapp to rudder-reports should be removed.

This was removed by the patch from https://github.com/Normation/rudder-packages/pull/275/files (attached to #4654). It has not yet been committed in nightlies, however.

Christophe, can you try and apply that patch and rebuild the packages? Otherwise, I will merge it before Monday, so Monday's nightlies include it.

Alternatively, as a temporary testing measure, you could just force rpm to not install that dependency... using something like "rpm --nodeps".

I must note that the following line in your pasted output is particularly appreciated by the team, and we were able to reproduce this behaviour by running it in our testing environment:

# Bisou, bon week-end ;-)
bash: syntax error near unexpected token `)'
bash: expecting "merci beaucoup, toi aussi !" 

Updating this to reflect the recent change from #4666: for now we have removed the dependency on rudder-reports.

This means that Rudder 2.11 nightlies will not automatically install rudder-reports, and therefore the PGSQL database. Caution!

This ticket must now serve as a basis to find a solution: how do we use packages like rudder-reports or a new "rudder-db-schema" to:

• Install, initialize and upgrade the database schema whenever rudder-webapp is updated
• Create the DB and depend on postgresql packages when rudder-server-root is installed but not when it is not and Rudder components are split across servers
• Ensure that the packages are installed in order - rudder-reports must be installed before rudder-webapp, or it will fail. The same applies for rudder-inventory-ldap actually.

There is no reference to postgresql in rudder-webapp scripts anymore.
This may have been solved by the packing of rudder-reports