chef / chef/knife-ec-backup

(beta4) Restore issue

Open
#58 20 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
32
Forks
28
PR merge metrics
No merged PRs in 30d

Description

Steps :

  • Install fresh Chef 12.0.1-1
  • Install beta4 (only beta2 is provided in the bundle)
  • Create acme org, admin org-admin and jdoe user (with chef-server-ctl cli)
  • bootstrap some nodes with few cookbooks (2 servers running a chef-server wrapper in my case)
  • Do a backup and save it :-)
  • Trash and install chef-server again with gem beta4
  • Get back and restore previous backup

Restore :

# /opt/opscode/embedded/bin/knife ec restore ./backup
WARNING: No knife configuration file found
WARNING: chef_server_root not found in knife configuration; using chef_server_url
Restoring users ...
WARNING: Skipping pivotal user.  To overwrite pivotal, pass --overwrite-pivotal.
Restoring the org admin data
Restoring the rest of the org
Updated /clients/acme-validator.json
Created /clients/chef-01.json
Created /clients/chef-02.json
Created /clients/acme-validator.json
ERROR: internal server error
Response: internal service error

Result :

  • org is restored
  • users are restored
  • groups/acl are restored
  • clients and validator key are restored
  • the rest is missing (cookbooks, nodes, ...)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with Chef 12.0.1-1, beta4, and the documented knife ec restore ./backup command. Inspect the restore stages after clients and the validator key are restored, then verify that cookbooks and nodes are restored without the internal server error.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
backend, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.