Bug #4167
closed
PostgreSQL migration of 'nodes execution' table can take a long time, a warning should be displayed
Added by Vincent MEMBRÉ about 11 years ago.
Updated over 9 years ago.
Description
When upgrading to rudder 2.8, a migration script is ran to create the new table containing all agent executions.
This script can be quite long (up to 20 minutes, but it would higher on more important installation).
During this time, no information are given to the user, making him worry for no reason.
A information should be displayed before running the migration script:
My proposition:
echo "INFO: Creating new table containing all nodes executions, this migration script can take a long time"
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/187
new proposition:
+ echo -n "INFO: Creating new table containing all nodes executions, this migration script can take a long time..."
psql -q -U rudder -h localhost -d rudder -f ${RUDDER_UPGRADE_TOOLS}/dbMigration-2.7-2.8-add-nodes-executions-storage.sql >/dev/null 2>&1
+ echo "Done."
PR updated: https://github.com/Normation/rudder-packages/pull/187
- Assignee changed from Jonathan CLARKE to Vincent MEMBRÉ
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:fc9a921456fa1f963a1da9b23c3de2d69fce5195.
Applied in changeset commit:6aa56000c7c022b556961bf208dbe1da2e64f3da.
- Subject changed from Migration of nodes execution can take a long time, a warning should be displayed to PostgreSQL migration of 'nodes execution' table can take a long time, a warning should be displayed
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.8.1, which was released today.
Check out:
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF