You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
I tried it with different policyfile on (mac and linux), coud not exactly replicate this.
Version:
Chef Workstation version: 21.2.278
Chef Infra Client version: 16.10.8
Chef InSpec version: 4.26.4
Chef CLI version: 3.1.1
Chef Habitat version: 1.6.181
Test Kitchen version: 2.10.0
Cookstyle version: 7.8.0
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
The text was updated successfully, but these errors were encountered: