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
Version:
TBI
Environment:
TBI
Scenario:
Pipeline involves running
chef installon 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 installon 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