sameersbn / sameersbn/docker-gitlab
Upgrade gitlab from v7.9.2 to v8.0.4 failed with restore data
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Since I didn't find a good place to ask questions, so here I came.
According to backup/restore sections in README.md, backup operation will backup all includes db and I also confirmed that from a backup tar, there is a db/ directory and a .sql file in it.
I'm using gitlab 7.9.2 and linked postgresql & redis with their own db volumes.
Now I'm trying to upgrade to gitlab 8.0.4 and wondering if I does restore from backup created by rake task, what will happen? does gitlab will re-write all db from the backup? or just use db in postgresql & redis?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the backup/restore sections in README.md and inspect the backup tar's db/ directory and SQL file. Determine how restoration behaves for the linked PostgreSQL and Redis volumes during the 7.9.2 to 8.0.4 upgrade, then document the confirmed behavior and any required steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql, redis
- Domain
- databases, devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100