Failure running `chef update` exit code 255
Open
Nobody has claimed this yet.
Priority: Critical
Triage: Confirmed
Type: Bug
- Dominant language
- Ruby
- Stars
- 18
- Forks
- 23
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
Version:
Latest
Environment:
MacOS (potentially Windows as well but need to verify)
Scenario:
We have an issue where running chef update exits the command with the output:
$ chef update
Attributes already up to date
Building policy frontend
Expanded run list: recipe[base], recipe[frontend], recipe[sigsci], recipe[audit]
Caching Cookbooks...
Installing base 1.0.19
[1] 76153 killed chef update
Steps to Reproduce:
TBA
Expected Result:
Regenerate the Policyfile.lock.json with the updated cookbooks/policies.
Actual Result:
The command is killed/exits with error code 255.
Reported by @jtimberman @tmonk42
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 reproducing chef update in the reported macOS environment and inspect the cookbook-caching and policy-generation steps shown in the output. Use Policyfile.lock.json as the completion check: the command should finish without exit code 255 and regenerate it with the updated cookbooks and policies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100