Actions
Bug #22315
closed"reportid" missing in PostgreSQL database after upgrade from v6.2.12 to v7.2.3
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I dislike using that feature
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
73
Name check:
To do
Fix check:
Checked
Regression:
No
Description
After upgrading the rudder-server from v6.2.12 to v7.2.3, the comliance bar on the nodes remained at 100% gray and the compliance reports tab no longer displayed any status.
The logs in /var/log/rudder/webapp/xxxx_xx_xx.stderrout.log contained many entries like:
ERROR com.normation.rudder.repository.jdbc.ReportsJdbcRepository - Error when trying to find reports by node: ERROR: column "reportid" does not exist Position: 52
The logs in /var/log/rudder/install/rudder-server-xxxxxxxxx.log contained:
Techniques have been updated, and update branch set to current state of the Techniques INFO: Upgrading PostgreSQL DB............ FAILED PostgreSQL service verification failed after 10 tries. ERROR INFO: Upgrading LDAP DB............ FAILED LDAP service verification failed after 10 tries. ERROR Plugins were not updated, because connection test is failing, please upgrade your plugins manually ERROR: The migration has failed in some steps. Check previous error messages. Please restart the failed service(s), and start the migration script again. (try service rudder-server restart) Once it is working, run: # /opt/rudder/bin/rudder-upgrade INFO: Correcting permissions on /var/rudder/configuration-repository... Done Running plugins upgrade scripts Restoring file ACLs FINISH: Rudder agent check ran properly, please look at messages above to see if there has been any error.
Running /opt/rudder/bin/rudder-upgrade again, like in #21705, fixed the problems.
Actions