Actions
Bug #11177
closed
Restore backup documentation is not correct
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Priority:
55
Name check:
Fix check:
Regression:
Description
In the backup documentation : https://www.rudder-project.org/doc-4.1/_migration_backups_and_restores.html
There are commands to backup and restore the postgresql content.
However, the command before is "service rudder stop" which stops postgres.
Updated by Benoît PECCATTE over 7 years ago
- Category set to Documentation
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Effort required set to Very Small
- Priority changed from 0 to 49
Updated by Alexis Mousset almost 7 years ago
- Target version set to 4.1.10
- Priority changed from 59 to 57
Updated by Alexis Mousset almost 7 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset almost 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-doc/pull/389
Updated by Alexis Mousset almost 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-doc|0492697aed134c3a0c72076b94c8f7ea75de4a20.
Updated by Vincent MEMBRÉ almost 7 years ago
- Status changed from Pending release to Released
- Priority changed from 57 to 55
This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.
- 4.1.10: Announce Changelog
- 4.2.4: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions