Bug #17591
closed
The webapp is unable to start after a fresh install
Added by Félix DALLIDET over 4 years ago.
Updated over 4 years ago.
Description
This is due to the script ordering in the packaging.
Rudder-init is run too soon, preventing the correct setup of the postgres password on debian.
If we move all the last part of the rudder-webapp-postinst to the server-root-server one we are sure that
rudder-init will be run after rudder-reports installation without needing an explicit dependency.
- Status changed from New to In progress
- Assignee set to Félix DALLIDET
- Status changed from In progress to Pending technical review
- Assignee changed from Félix DALLIDET to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2305
- Status changed from Pending technical review to New
- Assignee deleted (
Nicolas CHARLES)
- Pull Request deleted (
https://github.com/Normation/rudder-packages/pull/2305)
This is not suitable since it break distributed Rudder installs
- Target version changed from 6.1.0~rc2 to 6.1.0~rc3
- Related to Bug #17573: Error in technique editor just after install: No such file or directory: '/var/rudder/configuration-repository/ncf/generic_methods.json' added
- Related to Bug #17554: upgrading Rudder on Debian 9 from 5.0.17 to 6.1-rc1 tries to delete important folder added
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2307
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.0~rc3 which was released today.
- Fix check changed from To do to Checked
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by