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
Prod/Dev
[Details about the environment such as the Operating System, cookbook details, etc...]
Oracle Linux 7.9
Scenario:
During Backup restore process according to instruction if exist metadata.rb file and metadata.json, where metadata.rb version is lower than metadata.json, restore process somehow use metadata.rb version content instead of metadata.json. Chef server shows that latest version is same which in metadata.json, but clients downloading old version to cache.
After regular knife cookbook upload cookbook $name, everything fixed.
[What you are trying to achieve and you can't?]
Steps to Reproduce:
Create cookbook which have 2 different version in metadata
Backup
Start restore but fail
Start process again, and ask to fix failed restore.
Check content on hosts
Expected Result:
Versions content must be used from metadata.json, as most preferred
Actual Result:
Version from metadata.rb used for clients
The text was updated successfully, but these errors were encountered:
Version:
v3.0.1
[Version of the project installed]
Environment:
Prod/Dev
[Details about the environment such as the Operating System, cookbook details, etc...]
Oracle Linux 7.9
Scenario:
During Backup restore process according to instruction if exist metadata.rb file and metadata.json, where metadata.rb version is lower than metadata.json, restore process somehow use metadata.rb version content instead of metadata.json. Chef server shows that latest version is same which in metadata.json, but clients downloading old version to cache.
After regular knife cookbook upload cookbook $name, everything fixed.
[What you are trying to achieve and you can't?]
Steps to Reproduce:
Expected Result:
Versions content must be used from metadata.json, as most preferred
Actual Result:
Version from metadata.rb used for clients
The text was updated successfully, but these errors were encountered: