Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
slapos slapos
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !989

Closed
Created May 26, 2021 by Xavier Thompson@xavier_thompsonOwner
  • Report abuse
Report abuse

WIP: stack/erp5: Fix mariadb export and import

  • Overview 10
  • Commits 2
  • Changes 3

The exporter.exclude file and restore-from-backup script used when exporting and importing ERP5 as part of Webrunner resiliency were assuming that to re-initialize mariadb it was enough to delete the contents of srv/mariadb but not the folder itself, while the mariadb service assumes that if srv/mariadb exists it is in a valid state and only reinitialises it if it does not exist, meaning it will crash if it exists but is empty.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: erp5_fix_export
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7