sameersbn / sameersbn/docker-gitlab
Starting old version fails even if it is after restoration from backup of the version
Open
Nobody has claimed this yet.
wontfix
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I've encountered this issue after the following steps:
- GitLab v9.5.4 was running
- Created backup
- Updated to v10.0.2
- I decided to rollback GitLab to v9.5.4, because of some issues on v10.0.2
- Restored from backup with v9.5.4
- Tried to start v9.5.4 but it was disturbed
It said that we can't start v9.5.4 after v10.0.2, only upgrade is allowed.
Then I modified /home/git/data/tmp/VERSION (in the host PC) from 10.0.2 to 9.5.4.
After that, starting v9.5.4 was succeeded and works well.
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
Reproduce the reported sequence by running GitLab v9.5.4, upgrading to v10.0.2, restoring the backup, and starting v9.5.4 again. Inspect how /home/git/data/tmp/VERSION is read during startup; done means the restored older version starts correctly without manually changing VERSION.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100