Actions
Bug #15653
closed
Bug #15413: Autovacuum may never finish, or take more than one day, on busy Rudder instance, because of resources attrition
Bug #15416: Create migration script to remove autovacuum for ruddersysevents
Missing migration script for vacuum change
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
The parent ticket added the call in the rudder upgrade script, but the actual script is missing:
INFO: Checking PostgreSQL service status... OK INFO: Removing autovacuum configuration on ruddersysevents... /opt/rudder/share/upgrade-tools/dbMigration-5.0.x-5.0.13-remove-autovacuum-on-ruddersysevents.sql: No such file or directory INFO: End of migration script
Updated by François ARMAND about 5 years ago
The script is available in sources but not in packet => packaging problem.
Updated by François ARMAND about 5 years ago
- Assignee changed from Nicolas CHARLES to François ARMAND
Updated by François ARMAND about 5 years ago
- Status changed from New to In progress
Updated by François ARMAND about 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2056
Updated by François ARMAND about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|305e411fb762e9fef6ce762935fb691e9f5abae1.
Updated by François ARMAND about 5 years ago
- Target version changed from 5.0.14 to 5.0.13
Updated by François ARMAND about 5 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 5 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.13 which was released today.
Actions