Skip to content

Restore process merge cookbook version diring fix of failed restore #175

Description

@sosiskin2000

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:

  1. Create cookbook which have 2 different version in metadata
  2. Backup
  3. Start restore but fail
  4. Start process again, and ask to fix failed restore.
  5. 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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Status: UntriagedAn issue that has yet to be triaged.Type: BugDoes not work as expected.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions