Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Policyfile.lock.json differs for same Policyfile.rb intermittently #192

Open
vkarve-chef opened this issue Sep 14, 2021 · 1 comment
Open
Labels
Status: Untriaged An issue that has yet to be triaged. Type: Bug Does not work as expected.

Comments

@vkarve-chef
Copy link
Collaborator

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

@vkarve-chef vkarve-chef added Status: Untriaged An issue that has yet to be triaged. Type: Bug Does not work as expected. labels Sep 14, 2021
@i5pranay93
Copy link
Contributor

i5pranay93 commented Nov 25, 2021

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

Os - Linux

Here is screenshot
Screenshot 2021-11-25 at 5 45 22 PM
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Untriaged An issue that has yet to be triaged. Type: Bug Does not work as expected.
Projects
None yet
Development

No branches or pull requests

2 participants