Check and Replace Missing Migration Level File
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
As a Chef customer, I would like upgrades to stop failing.
An example upgrade would be Enterprise Chef 11.3.2 to Chef Server 12.1.2
The most common cause of a failed upgrade is a missing /var/opt/opscode/upgrade/migration-level file.
Currently, upgrades silently fail migrations when the migration-level file is missing and result in a broken chef server.
To fix the issue, the system should notice this missing file and replace it with the proper contents when on a backend system.
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 by tracing the upgrade handling for /var/opt/opscode/upgrade/migration-level and determine how the current migration level is selected on backend systems. Confirm the expected replacement contents and verify that an upgrade with the file missing no longer silently skips migrations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- backend, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100