install script from omnitruck fails when dpkg/yum/etc is temporarily locked
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 13
- Forks
- 55
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 8
Description
Version:
current at https://omnitruck.chef.io/install.sh
Environment:
I am running the script on Ubuntu 18.04 but the problem being described here is OS-agnostic and applies to all installation methods that use a package manager that uses a lock so that two package processes cannot run at once.
Scenario:
I am attempting to install chef using the install.sh script, coincidentally at the same time as another process is using dpkg (or another package manager).
Steps to Reproduce:
- launch a long/slow
dpkgoryumprocess - in another shell, run
install.sh
Expected Result:
install script waits for dpkg/yum to become unlocked
Actual Result:
Installing chef
installing with dpkg...
dpkg: error: dpkg frontend is locked by another process
Installation failed
Version:
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 current install.sh at https://omnitruck.chef.io/install.sh and trace how it invokes dpkg, yum, and other package managers. Reproduce the failure by running the script while a package-manager process holds its lock. Done means the installation waits for the lock to clear instead of immediately reporting an installation failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100