Policyfile.lock.json differs for same Policyfile.rb intermittently
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 18
- Forks
- 23
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
Version:
TBI
Environment:
TBI
Scenario:
Pipeline involves running chef install on Policyfile.rb. For same Policyfile.rb, sometimes a different Policyfile.lock.json is generated, with however a consistent revision Id.
Steps to Reproduce:
Run chef install on same Policyfile.rb multiple times.
Expected Result:
Policyfile.lock.json should be identical for all runs.
Actual Result:
Sometimes, the Policyfile.lock.json differs causing the git based pipeline to assume that the policy got updated. However, the revision ID and overall content is always consistent.
related customer issue - https://github.com/chef/customer-bugs/issues/472
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 the issue with repeated chef install runs on the same Policyfile.rb, using the related customer issue for context. Compare the generated Policyfile.lock.json files and trace the source of their intermittent differences. Done means identical lockfiles are generated consistently while preserving the expected revision ID and content.
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
- Mostly clear
- Newbie friendliness
- 35/100