mdxp / knife-backup Goto Github PK

Please fix this for Chef 12 or slap a big warning across it. First, it failed to recreate the users. This was fine for me as I only had 2 anyway. What I didn't realise until later was that it also didn't migrate the ACLs, which are a new thing in 12, so I run into chef/chef-server#63.

Not sure how to use -I option(--ignore-metadata-errors), I tried several ways, they all don't work. What's the correct format to use -I option?

This is on Ubuntu machine.

1. I installed gem on chef server for backup the server.

    sudo gem install knife-backup

1. Now I create a knife.rb file the following configuration.

   log_level :info
   log_location STDOUT
   validation_client_name 'chef-validator'
   validation_key '/etc/chef-server/chef-validator.pem'
   chef_server_url 'https://server_ip'

2. When I run the following command,

   sudo knife backup export -D /etc/chef/backups -c knife.rb
   

it is showing me error:-

/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/ohai-7.0.4/lib/ohai/loader.rb:188: warning: character class has [' without escape /opt/vagrant_ruby/lib/ruby/gems/1.8/gems/ohai-7.0.4/lib/ohai/loader.rb:188: warning: regexp has]' without escape
Backing up clients
ERROR: Your private key could not be loaded from /etc/chef/client.pem
Check your configuration file and ensure that your private key is readable

When doing a restore, nodes are overridden. clients are not. It warns that the client already exists but does not restore the previous data.

Say, a client is recreated but I want to revert to the backup. Sure, I can delete the client and then restore but it would easier if the restore deleted it and then recreated it. Or do an api.put() if the api.post() fails

So I am trying to restore everything... According to the usage, COMPONENT is optional.

$ knife backup restore -D backup -y -VV
WARNING: This will overwrite existing data!
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-backup-0.0.6/lib/chef/knife/backup_restore.rb:50:in `run': undefined method `keys' for #<Array:0x0000001ed97ee8> (NoMethodError)
        from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.4.4/lib/chef/knife.rb:460:in `run_with_pretty_exceptions'
        from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.4.4/lib/chef/knife.rb:173:in `run'
        from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.4.4/lib/chef/application/knife.rb:123:in `run'
        from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.4.4/bin/knife:25:in `<top (required)>'
        from /usr/bin/knife:23:in `load'
        from /usr/bin/knife:23:in `<main>'

If I specify the individual components, I do not get the exception.

When backing up from Hosted chef if a single item has permissions that prevent you from reading the object the entire component backup fails.

Example with users:

ERROR: You authenticated successfully to https://api.opscode.com/organizations/org as your_username but you are not authorized for this action
Response: You are not authorized to view user user_with_bad_perms

When restoring cookbooks using the following command:

admin@host:~$ ls -l /home/admin/backup_chef_server/cookbooks/
drwxr-xr-x 5 user2 user2 4096 Feb 25 17:15 apt-2.6.1
drwxr-xr-x 5 user2 user2 4096 Feb 25 17:15 dummy_cookbook-0.1.0
drwxr-xr-x 5 user2 user2 4096 Feb 25 17:15 dummy_cookbook-0.2.0
admin@host:~$ knife backup restore cookbooks roles environments clients users nodes -D /home/admin/backup_chef_server
/ffi-yajl/json_gem is deprecated, these monkeypatches will be dropped shortly
WARNING: This will overwrite existing data!
Do you want to restore backup, possibly overwriting exisitng data? (Y/N)y
=== Restoring cookbooks ===
ERROR: Errno::ENOENT: No such file or directory - /home/admin/backup_chef_server/cookbooks/dummy_cookbook

The reason is that the method responsible for restoring cookbooks creates a symlink from e.g. dummy_cookbook-0.1.0/ to dummy_cookbook/ and the symlink cannot be created if there are too restrictive permissions set.

It would be helpful to get an error about invalid permissions instead of not existing directory.

I got this error while restoring my backup from a Chef10 install to a Chef11:

ERROR: The data in your request was invalid
Response: Invalid value '0.5.0' for cookbook_versions

I found that my cookbooks versions constraints where not "hard" enough when I did not accept variations (like ~>, >=, etc.) and that I've specified an exact version (like "0.5.0").

I suppose this is a change in Chef 11.

I don't know if this would be correct to filter this kind of constraints in the backup and/or restore tho.

I've fixed my enviroments JSON dumps by filtering them with this small script:

require 'json'

# fake Chef::Environment class for JSON parse
class Chef
  class Environment
  end
end

ARGV.each do |zejsonfile|
  jsonout = ""
  File.open(zejsonfile, 'r') do |zefile|
    parsed = JSON.parse(zefile.read)
    if parsed.include? 'cookbook_versions'
      parsed['cookbook_versions'].each do |cookbook, version|
        if version =~ /^\d/
          parsed['cookbook_versions'][cookbook] = "= #{version}"
        end
      end
      jsonout = JSON.dump parsed
    end
  end
  unless jsonout == ""
    File.open(zejsonfile, 'w') do |zefile|
      zefile.write jsonout
    end
  end
end

Trying to restore a backup from a 10.26 server onto a new 11.0.8 install results in the following error on Ubuntu Precise (12.04):

(...)
=== Restoring cookbooks ===
Restoring cookbook ["openssl"]
DEBUG: Signing the request as transfer
DEBUG: Sending HTTP Request via GET to <chefserver>:443/cookbooks
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 200 OK
DEBUG: server: nginx/1.2.3
DEBUG: date: Tue, 30 Jul 2013 03:15:40 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 2
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.2.6
DEBUG: ---- End HTTP Status/Header Data ----
ERROR: knife encountered an unexpected error
This may be a bug in the 'backup restore' knife command or plugin
Please collect the output of this command with the `-VV` option before filing a bug report.
Exception: NameError: uninitialized constant Chef::CookbookLoader

Knife version is 11.6.

Because currently when there is a "depends" defined in the metadata.rb and it's not uploaded before, the result is an error:

Restoring cookbook ["mycookbook"]
Uploading mycookbook [1.4.0]
ERROR: Cookbook mycookbook depends on cookbooks which are not currently
ERROR: being uploaded and cannot be found on the server.
ERROR: The missing cookbook(s) are: 'somedependencycookbook' version '>= 1.0.0'

This is annoying because there is no order in which the cookbooks are restored. So there's no telling if the dependency will be restored before or after you actually need it.

When restoring over a hundred cookbooks+versions, if a single cookbook has syntax errors, the whole process bails out. This is pretty frustrating. It should skip if error and continue on with the rest, and just warn.

I'm trying to set this up to hit an older chef installation that I've inherited.

I'm installing chef-12.22.5-1, but after install knife-backup everything's been upgraded to version 14.11.21:

knife status
ERROR: The data in your request was invalid
Response: {"error": "400 - Bad Request: Chef Client version between 10 and 12" required. Your version of Chef is 14.11.21."}

I know there is already an issue similar to this one; but it's closed and sort of different.

So I'm running into this issue when I try to run: knife backup export -D ./backup

I'm using Ubuntu 14.04.4 LTS.

I'm using rvm; here is all the info I can think of:

$ rvm current
ruby-2.2.1

$ gem list | grep knife
knife-backup (0.0.12)
knife-ec2 (0.11.0.rc.0)
knife-rackspace (0.10.2)
knife-santoku (0.1.6)
knife-softlayer (0.4.0)
knife-spec (1.0.0)
knife-spork (1.5.1)
knife-vagrant (0.0.7)
knife-windows (0.8.5)

$ gem list | grep chef
chef (12.8.1, 11.18.12)
chef-config (12.8.1)
chef-zero (4.5.0, 2.2.1)

knife works without issue; it's just when I try to use knife backup where I have issues.

If I change out of the chef-repo it'll give me this:

$ knife backup
FATAL: Cannot find subcommand for: 'backup'
Available backup subcommands: (for details, knife SUB-COMMAND --help)

** BACKUP COMMANDS **
knife backup export [COMPONENT [COMPONENT ...]] [-D DIR] (options)
knife backup restore [COMPONENT [COMPONENT ...]] [-D DIR] (options)

So, I've thought maybe the knife or ruby versions are different from directories; but, they're both the same.

Any ideas?

see: http://stackoverflow.com/questions/2567670/ruby-json-pretty-generate-is-pretty-unpretty
It would be really nice for reading and editing the backups before restoring them.

RubyGems.org doesn't report a license for your gem. This is because it is not specified in the gemspec of your last release.

via e.g.

spec.license = 'MIT'
# or
spec.licenses = ['MIT', 'GPL-2']

Including a license in your gemspec is an easy way for rubygems.org and other tools to check how your gem is licensed. As you can image, scanning your repository for a LICENSE file or parsing the README, and then attempting to identify the license or licenses is much more difficult and more error prone. So, even for projects that already specify a license, including a license in your gemspec is a good practice. See, for example, how rubygems.org uses the gemspec to display the rails gem license.

There is even a License Finder gem to help companies/individuals ensure all gems they use meet their licensing needs. This tool depends on license information being available in the gemspec. This is an important enough issue that even Bundler now generates gems with a default 'MIT' license.

I hope you'll consider specifying a license in your gemspec. If not, please just close the issue with a nice message. In either case, I'll follow up. Thanks for your time!

Appendix:

If you need help choosing a license (sorry, I haven't checked your readme or looked for a license file), GitHub has created a license picker tool. Code without a license specified defaults to 'All rights reserved'-- denying others all rights to use of the code.
Here's a list of the license names I've found and their frequencies

p.s. In case you're wondering how I found you and why I made this issue, it's because I'm collecting stats on gems (I was originally looking for download data) and decided to collect license metadata,too, and make issues for gemspecs not specifying a license as a public service :). See the previous link or my blog post about this project for more information.

running the latest 0.0.8 version and when executing "knife backup export", nodes/environments/databags/roles gets backed up but cookbooks don't get backed up.

when I try to execute "knife backup export cookbooks", the same results happen.

I am trying run knife backup export on a chef 0.10.10 server, and I got the following errors, do you have any ideas?

knife backup export -D chef-backup/ -VV
DEBUG: Using configuration from /home/taklwu/.chef/knife.rb
/var/lib/gems/1.8/gems/knife-backup-0.0.5/lib/chef/knife/backup_export.rb:48:in run': undefined methodkeys' for #Array:0x7f0884bf9148 (NoMethodError)
from /usr/lib/ruby/vendor_ruby/chef/knife.rb:402:in run_with_pretty_exceptions' from /usr/lib/ruby/vendor_ruby/chef/knife.rb:168:inrun'
from /usr/lib/ruby/vendor_ruby/chef/application/knife.rb:123:in `run'
from /usr/bin/knife:24

I am attempting a restore and it seems like everything worked correctly except when it restored the cookbooks. It looks like it is trying to restore each version, but only really restores the newest version of the cookbook. The below example happened with every cookbook.

Restoring cookbook ["yum-repoforge"]
WARNING: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
WARNING: The cookbooks: yum-repoforge, yum-repoforge exist in multiple places in your cookbook_path.
A composite version of these cookbooks has been compiled for uploading.

IMPORTANT: In a future version of Chef, this behavior will be removed and you will no longer
be able to have the same version of a cookbook in multiple places in your cookbook_path.
WARNING: The affected cookbooks are located:
yum-repoforge:
  /Users/pkringle/chef-backup_20150325/cookbooks/yum-repoforge
  /Users/pkringle/chef-backup_20150325/cookbooks/yum-repoforge-0.4.0
  /Users/pkringle/chef-backup_20150325/cookbooks/yum-repoforge-0.5.0
WARNING: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
Uploading yum-repoforge  [0.5.0]
Uploaded 1 cookbook.
Restoring cookbook ["yum-repoforge"]
WARNING: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
WARNING: The cookbooks: yum-repoforge, yum-repoforge exist in multiple places in your cookbook_path.
A composite version of these cookbooks has been compiled for uploading.

IMPORTANT: In a future version of Chef, this behavior will be removed and you will no longer
be able to have the same version of a cookbook in multiple places in your cookbook_path.
WARNING: The affected cookbooks are located:
yum-repoforge:
  /Users/pkringle/chef-backup_20150325/cookbooks/yum-repoforge
  /Users/pkringle/chef-backup_20150325/cookbooks/yum-repoforge-0.4.0
  /Users/pkringle/chef-backup_20150325/cookbooks/yum-repoforge-0.5.0
WARNING: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
Uploading yum-repoforge  [0.5.0]
Uploaded 1 cookbook.

I checked the metadata in the cookbooks to make sure they were correct.

$ grep version /Users/pkringle/chef-backup_20150325/cookbooks/yum-repoforge-0.*.0/metadata.json 
/Users/pkringle/chef-backup_20150325/cookbooks/yum-repoforge-0.4.0/metadata.json:  "version": "0.4.0",
/Users/pkringle/chef-backup_20150325/cookbooks/yum-repoforge-0.5.0/metadata.json:  "version": "0.5.0",

I am using chef / knife version

$ knife --version
Chef: 12.1.1

And restoring to chef server version 11.1.6-1 on Ubuntu 14.04

Thoughts? Is it something I am doing?

Thanks.

Hi,

I followed the instructions to install knife-backup but cannot execute the back command.

knife backup --help
FATAL: Cannot find sub command for: 'backuo --help'
Available subcommands: (for details, knife SUB-COMMAND --help)

When I do a 'gem list' I see knife-backup installed. Can you assist, please?

My knife/chef version: 11.4.4.

Regards,
Sebastian

I was getting the following error when trying to restore using 0.0.9:

knife backup -VV restore -D /Users/travis/chef-backup -c /gc/gcchef/.chef/knife-new.rb
WARNING: This will overwrite existing data!
Do you want to restore backup, possibly overwriting exisitng data? (Y/N)Y
/Users/travis/.rvm/rubies/ruby-2.1.1/lib/ruby/gems/2.1.0/gems/knife-backup-0.0.9/lib/chef/knife/backup_restore.rb:116:in `clients': undefined method `create_id=' for JSON:Module (NoMethodError)
    from /Users/travis/.rvm/rubies/ruby-2.1.1/lib/ruby/gems/2.1.0/gems/knife-backup-0.0.9/lib/chef/knife/backup_restore.rb:52:in `block in run'
    from /Users/travis/.rvm/rubies/ruby-2.1.1/lib/ruby/gems/2.1.0/gems/knife-backup-0.0.9/lib/chef/knife/backup_restore.rb:52:in `each'
    from /Users/travis/.rvm/rubies/ruby-2.1.1/lib/ruby/gems/2.1.0/gems/knife-backup-0.0.9/lib/chef/knife/backup_restore.rb:52:in `run'
    from /Users/travis/.rvm/rubies/ruby-2.1.1/lib/ruby/gems/2.1.0/gems/chef-11.14.0.rc.2/lib/chef/knife.rb:493:in `run_with_pretty_exceptions'
    from /Users/travis/.rvm/rubies/ruby-2.1.1/lib/ruby/gems/2.1.0/gems/chef-11.14.0.rc.2/lib/chef/knife.rb:174:in `run'
    from /Users/travis/.rvm/rubies/ruby-2.1.1/lib/ruby/gems/2.1.0/gems/chef-11.14.0.rc.2/lib/chef/application/knife.rb:139:in `run'
    from /Users/travis/.rvm/rubies/ruby-2.1.1/lib/ruby/gems/2.1.0/gems/chef-11.14.0.rc.2/bin/knife:25:in `<top (required)>'
    from /Users/travis/.rvm/gems/ruby-2.1.1/bin/knife:23:in `load'
    from /Users/travis/.rvm/gems/ruby-2.1.1/bin/knife:23:in `<main>'
    from /Users/travis/.rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in `eval'
    from /Users/travis/.rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in `<main>'

I am a total Ruby novice, but I was able to fix this for myself by adding require 'JSON' to the top of backup_restore.rb. Didn't want to send a PR because I figured there was probably something fundamentally wrong with that approach.

Hello,

Using chef-12.0.3-1.x86_64 I've got:

# knife backup export -D /tmp/ -c backup.rb -V
...
Backing up nodes babilonia
Backing up nodes mchat
INFO: HTTP Request Returned 403 Forbidden: error
ERROR: You authenticated successfully to https://chef.xxxx.com/organizations/xxxx as backup but you are not authorized for this action
Response:  missing read permission

The user is an admin:

$ knife group show admins | grep backup
  user_usag: backup

What can I do? Thanks a lot!

When doing an export, the "public_key" value is null. Why is this? After I imported back to my new server, none of my original clients could check in

It would be nice to use this plugin to sync all the changes done by someone on the chef webinterface back to the chef-repo. For this purpose we need the original (cookbook) directory name without the version number that is already stored in the metadata.rb.

I get to backing up users and then:

ERROR: JSON::ParserError: Unsupported json_class type 'Chef::WebUIUser'

My knife install is 11.x via omnibus, and I had to have gem be conservative to get chef-backup installed
looking into collecting more debug info now....

I did a backup of my production box and moved and extracted the tgz to my testing box.

root@testbox-chef:/var/log/chef-server# chef-server-ctl test
Configuring logging...
Creating platform...
Starting Pedant Run: 2014-12-31 18:29:35 UTC
setting up rspec config for #<Pedant::OpenSourcePlatform:0x0000000298b050>
Configuring RSpec for Open-Source Tests
 _______  _______  _______  _______  _______  ______   _______
|       ||       ||       ||       ||       ||      | |       |
|   _   ||    _  ||  _____||       ||   _   ||  _    ||    ___|
|  | |  ||   |_| || |_____ |       ||  | |  || | |   ||   |___
|  |_|  ||    ___||_____  ||      _||  |_|  || |_|   ||    ___|
|       ||   |     _____| ||     |_ |       ||       ||   |___
|_______||___|    |_______||_______||_______||______| |_______|

     _______  _______  ______   _______  __    _  _______
    |       ||       ||      | |   _   ||  |  | ||       |
    |    _  ||    ___||  _    ||  |_|  ||   |_| ||_     _|
    |   |_| ||   |___ | | |   ||       ||       |  |   |
    |    ___||    ___|| |_|   ||       ||  _    |  |   |
    |   |    |   |___ |       ||   _   || | |   |  |   |
    |___|    |_______||______| |__| |__||_|  |__|  |___|

                    "Accuracy Over Tact"

                  === Testing Environment ===
                 Config File: /var/opt/chef-server/chef-pedant/etc/pedant_config.rb
       HTTP Traffic Log File: /var/log/chef-server/chef-pedant/http-traffic.log

Running tests from the following directories:
/opt/chef-server/embedded/service/chef-pedant/spec/api
Ruby?  Erlang? true
Run options:
  include {:focus=>true, :smoke=>true}
  exclude {:platform=>:multitenant, :cleanup=>true}
Creating client pedant_admin_client...
Encountered an error attempting to create client pedant_admin_client
Response Code was: 401
Response Body was: {"error":["Invalid signature for user or client 'admin'"]}
Exception during Pedant credentials setup

Anyone else get this? It also has the effect that clients of the testing box see:

>   Authentication Error:
>   ---------------------
>   Failed to authenticate to the chef server (http 401).
>   
>   Server Response:
>   ----------------
>   Invalid signature for user or client 'chef-validator'
>
>  Relevant Config Settings:
>  -------------------------
>  chef_server_url         "https://...:443"
>  validation_client_name  "chef-validator"
>  validation_key          "/etc/chef/validation.pem"
>  
>  If these settings are correct, your validation_key may be invalid.

Thanks, M.

I have successfully tested restore with this. Thanks for a great tool. One odd issue is that some files got truncated during restored. The file we found was web.xml template for Tomcat which is fairly long. Could this be something like an HTTP POST size limitation?

WARNING: This will overwrite existing data!
Do you want to restore backup, possibly overwriting exisitng data? (Y/N) Y
=== Restoring clients ===
ruby: yajl_parser.c:151: yajl_do_parse: Assertion `(hand->stateStack).used > 0' failed.
Aborted

I am using knife backup - restore plugin with following configuration

knife plugin version : 0.0.12
chef server version : 11.18.12

It has been found that, after restore, certain node attributes are not visible when we do "knife show node" command.

I have virtual machine, which has following attributes.

Command : knife node show falRhel6x64.ammpilot.FALCON.release.ibm.com
Output

Node Name: falRhel6x64.ammpilot.FALCON.release.ibm.com
Environment: _default
FQDN: falRhel6x64.ammpilot.FALCON.release.ibm.com
IP: 159.8.215.239
Run List: recipe[zabbix-agent::linux], role[SetupPatchingNode]
Roles: ScanForPatches
Recipes: patchservice_operations::ScanEndpoints
Platform: redhat 7.2
Tags:

When I do backup using knife backup and proceed with restore operation, same node shows following attributes when it is queried

[root@localhost ~]# knife node show falRhel6x64.ammpilot.FALCON.release.ibm.com
Node Name: falRhel6x64.ammpilot.FALCON.release.ibm.com
Environment: _default
FQDN:
IP:
Run List: recipe[zabbix-agent::linux], role[SetupPatchingNode]
Roles:
Recipes:
Platform:
Tags:

If you see, certain attributes are missing. It has been seen that, certain JSON block is missing.

Do you have any idea?

taklwu@localhost:~$ sudo knife backup restore -D chef_server_backup -y -VV
[sudo] password for taklwu:
WARNING: This will overwrite existing data!
=== Restoring clients ===
=== Restoring nodes ===
=== Restoring roles ===
=== Restoring data bags ===
=== Restoring environments ===
=== Restoring cookbooks ===
Restoring cookbook twisterCloud
DEBUG: Signing the request as admin
DEBUG: Sending HTTP Request via GET to localhost:8000/cookbooks
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 200 OK
DEBUG: date: Thu, 20 Jun 2013 20:38:16 GMT
DEBUG: content-length: 2
DEBUG: server: MochiWeb/1.1 WebMachine/1.9.0 (someone had painted it blue)
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.2.6
DEBUG: content-type: application/json
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: No chefignore file found at /home/taklwu/chef_server_backup/cookbooks/chefignore no files will be ignored
Uploading twisterCloud [0.0.1]
INFO: Validating ruby files
INFO: Validating templates
INFO: Syntax OK
INFO: Saving twisterCloud
DEBUG: Signing the request as admin
DEBUG: Sending HTTP Request via POST to localhost:8000/sandboxes
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 201 Created
DEBUG: date: Thu, 20 Jun 2013 20:38:16 GMT
DEBUG: content-length: 1062
DEBUG: location: http://localhost:8000/sandboxes/000000000000d74146cd3eea68e84e08
DEBUG: server: MochiWeb/1.1 WebMachine/1.9.0 (someone had painted it blue)
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.2.6
DEBUG: content-type: application/json
DEBUG: ---- End HTTP Status/Header Data ----
INFO: Uploading files
INFO: Uploading /home/taklwu/chef_server_backup/cookbooks/twisterCloud/README.md (checksum hex = 6e21094b7a920e374e7261f50e9c4eef) to https://localhost:443/bookshelf/organization-00000000000000000000000000000000/checksum-6e21094b7a920e374e7261f50e9c4eef?AWSAccessKeyId=a2426188bfc429aaafe32ccd60a03c909b480627&Expires=1371761596&Signature=C//2Ax7NIULH0XbzJBtK4Xa2UtI%3D
INFO: Uploading /home/taklwu/chef_server_backup/cookbooks/twisterCloud/recipes/default.rb (checksum hex = 9677cffd448c89aff9736f7a536d6563) to https://localhost:443/bookshelf/organization-00000000000000000000000000000000/checksum-9677cffd448c89aff9736f7a536d6563?AWSAccessKeyId=a2426188bfc429aaafe32ccd60a03c909b480627&Expires=1371761596&Signature=iVgKIRyX4qno7E67gSJdSRwbeVk%3D
INFO: Uploading /home/taklwu/chef_server_backup/cookbooks/twisterCloud/metadata.rb (checksum hex = ce7df143229c7e43c4b1ce8cd017f445) to https://localhost:443/bookshelf/organization-00000000000000000000000000000000/checksum-ce7df143229c7e43c4b1ce8cd017f445?AWSAccessKeyId=a2426188bfc429aaafe32ccd60a03c909b480627&Expires=1371761596&Signature=VLqRqxwG/R/Kj0Dz4h8KNTkuMO8%3D
/usr/lib/ruby/1.8/net/http.rb:586:in connect': Connection reset by peer - SSL_connect (Errno::ECONNRESET) from /usr/lib/ruby/1.8/net/http.rb:586:inconnect'
from /usr/lib/ruby/1.8/net/http.rb:553:in do_start' from /usr/lib/ruby/1.8/net/http.rb:542:instart'
from /var/lib/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:172:in transmit' from /var/lib/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:64:inexecute'
from /var/lib/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in execute' from /var/lib/gems/1.8/gems/rest-client-1.6.7/lib/restclient/resource.rb:80:input'
from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/cookbook_uploader.rb:142:in uploader_function_for' from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/cookbook_uploader.rb:25:incall'
from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/cookbook_uploader.rb:25:in setup_worker_threads' from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/cookbook_uploader.rb:24:inloop'
from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/cookbook_uploader.rb:24:in setup_worker_threads' from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/cookbook_uploader.rb:23:ininitialize'
from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/cookbook_uploader.rb:23:in new' from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/cookbook_uploader.rb:23:insetup_worker_threads'
from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/mixin/from_file.rb:30:in map' from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/cookbook_uploader.rb:22:ineach'
from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/cookbook_uploader.rb:22:in map' from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/cookbook_uploader.rb:22:insetup_worker_threads'
from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/cookbook_uploader.rb:75:in upload_cookbooks' from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/knife/cookbook_upload.rb:230:inupload'
from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/knife/cookbook_upload.rb:121:in run' from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/knife/cookbook_upload.rb:118:ineach'
from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/knife/cookbook_upload.rb:118:in run' from /var/lib/gems/1.8/gems/knife-backup-0.0.7/lib/chef/knife/backup_restore.rb:146:incookbooks'
from /var/lib/gems/1.8/gems/knife-backup-0.0.7/lib/chef/knife/backup_restore.rb:135:in each' from /var/lib/gems/1.8/gems/knife-backup-0.0.7/lib/chef/knife/backup_restore.rb:135:incookbooks'
from /var/lib/gems/1.8/gems/knife-backup-0.0.7/lib/chef/knife/backup_restore.rb:51:in send' from /var/lib/gems/1.8/gems/knife-backup-0.0.7/lib/chef/knife/backup_restore.rb:51:inrun'
from /var/lib/gems/1.8/gems/knife-backup-0.0.7/lib/chef/knife/backup_restore.rb:51:in each' from /var/lib/gems/1.8/gems/knife-backup-0.0.7/lib/chef/knife/backup_restore.rb:51:inrun'
from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/knife.rb:460:in run_with_pretty_exceptions' from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/knife.rb:173:inrun'
from /var/lib/gems/1.8/gems/chef-11.4.4/lib/chef/application/knife.rb:123:in run' from /var/lib/gems/1.8/gems/chef-11.4.4/bin/knife:25 from /usr/local/bin/knife:19:inload'
from /usr/local/bin/knife:19

when I export a user I get a file like this:
{
"name":"",
"public_key":"-----BEGIN PUBLIC KEY-----\nxxx\n-----END PUBLIC KEY-----\n\n",
"admin":false
}
the value for the name is always empty and it looks like ChefServer12 uses username instead of name which also prevents the restore.

Getting this when restoring a cookbook with Chef 11.6.0

=== Restoring cookbooks ===
Restoring cookbook ["apache2"]
DEBUG: Signing the request as admin
DEBUG: Sending HTTP Request via GET to testing:443/cookbooks
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 200 OK
DEBUG: server: nginx/1.2.3
DEBUG: date: Tue, 13 Aug 2013 23:05:38 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 2
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.2.6
DEBUG: ---- End HTTP Status/Header Data ----
/usr/local/opt/rbenv/versions/1.9.3-p429/lib/ruby/gems/1.9.1/gems/chef-11.6.0/lib/chef/knife/cookbook_upload.rb:180:in `cookbook_repo': uninitialized constant Chef::CookbookLoader (NameError)
    from /usr/local/opt/rbenv/versions/1.9.3-p429/lib/ruby/gems/1.9.1/gems/chef-11.6.0/lib/chef/knife/cookbook_upload.rb:163:in `block in cookbooks_to_upload'
    from /usr/local/opt/rbenv/versions/1.9.3-p429/lib/ruby/gems/1.9.1/gems/chef-11.6.0/lib/chef/knife/cookbook_upload.rb:160:in `each'
    from /usr/local/opt/rbenv/versions/1.9.3-p429/lib/ruby/gems/1.9.1/gems/chef-11.6.0/lib/chef/knife/cookbook_upload.rb:160:in `cookbooks_to_upload'
    from /usr/local/opt/rbenv/versions/1.9.3-p429/lib/ruby/gems/1.9.1/gems/chef-11.6.0/lib/chef/knife/cookbook_upload.rb:119:in `run'
    from /Users/mkent/git/knife-backup/lib/chef/knife/backup_restore.rb:146:in `block in cookbooks'
    from /Users/mkent/git/knife-backup/lib/chef/knife/backup_restore.rb:135:in `each'
    from /Users/mkent/git/knife-backup/lib/chef/knife/backup_restore.rb:135:in `cookbooks'
    from /Users/mkent/git/knife-backup/lib/chef/knife/backup_restore.rb:51:in `block in run'
    from /Users/mkent/git/knife-backup/lib/chef/knife/backup_restore.rb:51:in `each'
    from /Users/mkent/git/knife-backup/lib/chef/knife/backup_restore.rb:51:in `run'
    from /usr/local/opt/rbenv/versions/1.9.3-p429/lib/ruby/gems/1.9.1/gems/chef-11.6.0/lib/chef/knife.rb:466:in `run_with_pretty_exceptions'
    from /usr/local/opt/rbenv/versions/1.9.3-p429/lib/ruby/gems/1.9.1/gems/chef-11.6.0/lib/chef/knife.rb:173:in `run'
    from /usr/local/opt/rbenv/versions/1.9.3-p429/lib/ruby/gems/1.9.1/gems/chef-11.6.0/lib/chef/application/knife.rb:123:in `run'
    from /usr/local/opt/rbenv/versions/1.9.3-p429/lib/ruby/gems/1.9.1/gems/chef-11.6.0/bin/knife:25:in `<top (required)>'
    from /Users/mkent/git/chef-repo/bin/knife:16:in `load'
    from /Users/mkent/git/chef-repo/bin/knife:16:in `<main>'

looks like a require got shifted in in Chef.

I am trying to use knife backup-restore plugin. During restore operation, it is failing with error

json_create': undefined methodeach' for nil:NilClass (NoMethodError)

Here is the "knife backup restore" operation output with -VV option.

[root@sandbox-pilot ~]# docker exec chefserver.falcon.ibm.com knife backup restore -y -D /media/ibm/backup/my_backup -VV
WARNING: This will overwrite existing data!
=== Restoring clients ===
Restoring clients from /media/ibm/backup/my_backup/clients/Pilot-test-2.falcon.ibm.com.json
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_request
DEBUG: Signing the request as admin
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_request
DEBUG: Initiating POST to https://chefserver.falcon.ibm.com:6443/clients
DEBUG: ---- HTTP Request Header Data: ----
DEBUG: Content-Type: application/json
DEBUG: Accept: application/json
DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
DEBUG: X-OPS-USERID: admin
DEBUG: X-OPS-TIMESTAMP: 2016-06-16T11:10:15Z
DEBUG: X-OPS-CONTENT-HASH: h666Z/pjvyTr1tSOcLR0l6pHeTs=
DEBUG: X-OPS-AUTHORIZATION-1: ltER8yy5rOAT9FuW87axsnG22x4x8Ub8X+sdoOa5m1UJ7nGw8kV2qYTxnf/T
DEBUG: X-OPS-AUTHORIZATION-2: ymS+9i+zULjL7x+gmtJZKMTwojXZbuRAa8ek7VhF0oVi44XGMY36JUK02bhA
DEBUG: X-OPS-AUTHORIZATION-3: BKVZNHtAznnELvyGKIJURMqpjG98v4aI4uGjHAx8ztta6eictTUTLr5JGLQS
DEBUG: X-OPS-AUTHORIZATION-4: 6PyJzcU2LamgENX7qoYThXko+vad7FPNiCtRpWHPVRvkzt7+ooHO03viDv7t
DEBUG: X-OPS-AUTHORIZATION-5: GU0UzX9lioU9DhrQb3q17Q/SUGjcHVtDfW01b3Rc2qPqGQS15cNgsDKnVBWx
DEBUG: X-OPS-AUTHORIZATION-6: 5bmsPW8Py0G/7cO6NOP0OhlATDy2cnsoWgRyn1MkOQ==
DEBUG: HOST: chefserver.falcon.ibm.com:6443
DEBUG: X-REMOTE-REQUEST-ID: 93922054-009b-4733-a14c-64d80f32d40b
DEBUG: Content-Length: 546
DEBUG: ---- End HTTP Request Header Data ----
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 409 Conflict
DEBUG: server: nginx/1.4.4
DEBUG: date: Thu, 16 Jun 2016 11:10:15 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 35
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.4.1
DEBUG: location: http://chefserver.falcon.ibm.com:6443/clients/Pilot-test-2.falcon.ibm.com
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_response
DEBUG: Content-Length validated correctly.
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
INFO: HTTP Request Returned 409 Conflict: Client already exists
Restoring clients from /media/ibm/backup/my_backup/clients/pilotcl2.falcon.ibm.com.json
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request
WARNING: client[Pilot-test-2.falcon.ibm.com] already exists; skipping
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_request
DEBUG: Signing the request as admin
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_request
DEBUG: Initiating POST to https://chefserver.falcon.ibm.com:6443/clients
DEBUG: ---- HTTP Request Header Data: ----
DEBUG: Content-Type: application/json
DEBUG: Accept: application/json
DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
DEBUG: X-OPS-USERID: admin
DEBUG: X-OPS-TIMESTAMP: 2016-06-16T11:10:15Z
DEBUG: X-OPS-CONTENT-HASH: CxxkvAem/S8LCKdynGpx/AEnIuY=
DEBUG: X-OPS-AUTHORIZATION-1: qz/gp/+pqRP5KxnS2cDSY7hhHtQeaZrqgknDiWGtp1VdvowzxbMYMDSex8tu
DEBUG: X-OPS-AUTHORIZATION-2: dQA6Dbtp1Ty31vaWE4DwfWCG0K9WB0a5hkdOo+lmtJDaPt8+cIGwVpfol+Ow
DEBUG: X-OPS-AUTHORIZATION-3: Fu4ldQV3K6ixM2W6zodRqXGk4KiMleA4raNT5cNDLXTL41D0sokwoaXkUdJJ
DEBUG: X-OPS-AUTHORIZATION-4: 4wpVP9h5FsSbBtPfvrfM46Zfj/YOYfaPV493atDC+75ElywSBNhu10D+XG9Q
DEBUG: X-OPS-AUTHORIZATION-5: tU1jgTuhUGsKMl92FPhDD6akSrWpknmIf2e1R+Jg6QXNmJ0UFcjAe6XPULln
DEBUG: X-OPS-AUTHORIZATION-6: e6IEwJjJEN5/Cu63Ms+NkrXqvIzzwtMP1rI3TlGOdg==
DEBUG: HOST: chefserver.falcon.ibm.com:6443
DEBUG: X-REMOTE-REQUEST-ID: 93922054-009b-4733-a14c-64d80f32d40b
DEBUG: Content-Length: 542
DEBUG: ---- End HTTP Request Header Data ----
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 409 Conflict
DEBUG: server: nginx/1.4.4
DEBUG: date: Thu, 16 Jun 2016 11:10:15 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 35
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.4.1
DEBUG: location: http://chefserver.falcon.ibm.com:6443/clients/pilotcl2.falcon.ibm.com
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_response
DEBUG: Content-Length validated correctly.
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
INFO: HTTP Request Returned 409 Conflict: Client already exists
WARNING: client[pilotcl2.falcon.ibm.com] already exists; skipping
Restoring clients from /media/ibm/backup/my_backup/clients/pilotcl1.falcon.ibm.com.json
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_request
DEBUG: Signing the request as admin
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_request
DEBUG: Initiating POST to https://chefserver.falcon.ibm.com:6443/clients
DEBUG: ---- HTTP Request Header Data: ----
DEBUG: Content-Type: application/json
DEBUG: Accept: application/json
DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
DEBUG: X-OPS-USERID: admin
DEBUG: X-OPS-TIMESTAMP: 2016-06-16T11:10:15Z
DEBUG: X-OPS-CONTENT-HASH: fSNU5jOSoXnOerSU4w+z7GyzpLs=
DEBUG: X-OPS-AUTHORIZATION-1: JDFI4Ft1yHRGgqzAg5rZzSsTSIQ7qieFcZ2aBP7bbXuzJI4kF1F27ogJSsrH
DEBUG: X-OPS-AUTHORIZATION-2: q8kcXaJjx19p76frH+/qj80RSojdmZEcTfllHtw6g350dcJBfwfisCtdintB
DEBUG: X-OPS-AUTHORIZATION-3: CuJYbE2dW70vf+ge357nNZcnAhLRSF7L1P4koRUm/qGI50laeTIUNrZfPx/A
DEBUG: X-OPS-AUTHORIZATION-4: Pbl5Sy6wFGZRlHqzzDxlEfRNtzzUMHrM2C+E7gHa69JbLrCKnp07O+Gu823V
DEBUG: X-OPS-AUTHORIZATION-5: VvINrb9ofdDOXA/1JQamqWP4iUpHwZLeS6hhvCWzKhUR6I8ZS8eXYYuZtZab
DEBUG: X-OPS-AUTHORIZATION-6: WckTY6GeXZyMfVoLEv1XhPS0eVMxpVZz6Yk6zYyPQw==
DEBUG: HOST: chefserver.falcon.ibm.com:6443
DEBUG: X-REMOTE-REQUEST-ID: 93922054-009b-4733-a14c-64d80f32d40b
DEBUG: Content-Length: 542
DEBUG: ---- End HTTP Request Header Data ----
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 409 Conflict
DEBUG: server: nginx/1.4.4
DEBUG: date: Thu, 16 Jun 2016 11:10:15 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 35
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.4.1
DEBUG: location: http://chefserver.falcon.ibm.com:6443/clients/pilotcl1.falcon.ibm.com
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_response
DEBUG: Content-Length validated correctly.
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
INFO: HTTP Request Returned 409 Conflict: Client already exists
Restoring clients from /media/ibm/backup/my_backup/clients/chef-webui.json
WARNING: client[pilotcl1.falcon.ibm.com] already exists; skipping
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_request
DEBUG: Signing the request as admin
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_request
DEBUG: Initiating POST to https://chefserver.falcon.ibm.com:6443/clients
DEBUG: ---- HTTP Request Header Data: ----
DEBUG: Content-Type: application/json
DEBUG: Accept: application/json
DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
DEBUG: X-OPS-USERID: admin
DEBUG: X-OPS-TIMESTAMP: 2016-06-16T11:10:15Z
DEBUG: X-OPS-CONTENT-HASH: cHSHZJcCSkw1/MAEiyVqzFK6WOM=
DEBUG: X-OPS-AUTHORIZATION-1: zON/lNDwi2Oi5mZhnzokhGINUBLAlJ97Pke24eZ1RHMTn9ZgXR3ggaklcXeX
DEBUG: X-OPS-AUTHORIZATION-2: S7FcjNuxohomdHe9rZEjp+LBGN2nZR4GM0Sn3aEbRlbEYPEac1OvNTJ44epB
DEBUG: X-OPS-AUTHORIZATION-3: Ol8VGHimY8iRAoCfuN4BFN1iNaB8gqSzEyX8sy/gV6tZXkeHAAxIZRpgPMfT
DEBUG: X-OPS-AUTHORIZATION-4: EEyIuTF9I82EdAkxhEz76feIELj7PYN7Ye1LHuXmzZdgY6Z8ZwYunD3K3YBx
DEBUG: X-OPS-AUTHORIZATION-5: PwP5XMQ2EQ9nwKCrtUPUeq1nDmpj9bFhLdfrUBrpOwnqOFww2Lei8sEzYxt7
DEBUG: X-OPS-AUTHORIZATION-6: Fmdi1s1cd3svz/dlnxGAabXmE7AuNAvCM/oKbDGugw==
DEBUG: HOST: chefserver.falcon.ibm.com:6443
DEBUG: X-REMOTE-REQUEST-ID: 93922054-009b-4733-a14c-64d80f32d40b
DEBUG: Content-Length: 528
DEBUG: ---- End HTTP Request Header Data ----
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 409 Conflict
DEBUG: server: nginx/1.4.4
DEBUG: date: Thu, 16 Jun 2016 11:10:15 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 35
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.4.1
DEBUG: location: http://chefserver.falcon.ibm.com:6443/clients/chef-webui
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_response
DEBUG: Content-Length validated correctly.
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
INFO: HTTP Request Returned 409 Conflict: Client already exists
Restoring clients from /media/ibm/backup/my_backup/clients/falW2k12r2x64.ammpilot.FALCON.release.ibm.com.json
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_request
DEBUG: Signing the request as admin
WARNING: client[chef-webui] already exists; skipping
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_request
DEBUG: Initiating POST to https://chefserver.falcon.ibm.com:6443/clients
DEBUG: ---- HTTP Request Header Data: ----
DEBUG: Content-Type: application/json
DEBUG: Accept: application/json
DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
DEBUG: X-OPS-USERID: admin
DEBUG: X-OPS-TIMESTAMP: 2016-06-16T11:10:15Z
DEBUG: X-OPS-CONTENT-HASH: YOfhNinE2458Mp1sZOj4IfyTmVg=
DEBUG: X-OPS-AUTHORIZATION-1: 1MA3mpmemAA/ClXbdn7ujnQQ+pEfKl/VS2FEp+uaMU2ERfu5lJB6ZPteaQxC
DEBUG: X-OPS-AUTHORIZATION-2: 0uB1L3L2K8gfLPgqLWIm/P45Nq6/u4RWzgvr924o/e0jYZtyaOh9Pwmp4OfH
DEBUG: X-OPS-AUTHORIZATION-3: SIghFO+5wz16ss0xb2+UW/oWaGSR6Vq+tXFM/5gGwWHFEwf2KB8itwwqcxJF
DEBUG: X-OPS-AUTHORIZATION-4: hccQ9WqdYbRxTbbACRGLq8SfkB3Hu8NjHq9mIM9OETcgXaYomjp6RTKnOBJG
DEBUG: X-OPS-AUTHORIZATION-5: zJiKKdgw1kFgduAYIbdYy5ARmnRBAhInu6918DzJbUvqUDumt+uWfYQE8kna
DEBUG: X-OPS-AUTHORIZATION-6: C2Z/72Sfb7BMX+kqjvik8qADLkEVQR85ZC89cznpsw==
DEBUG: HOST: chefserver.falcon.ibm.com:6443
DEBUG: X-REMOTE-REQUEST-ID: 93922054-009b-4733-a14c-64d80f32d40b
DEBUG: Content-Length: 564
DEBUG: ---- End HTTP Request Header Data ----
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 409 Conflict
DEBUG: server: nginx/1.4.4
DEBUG: date: Thu, 16 Jun 2016 11:10:16 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 35
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.4.1
DEBUG: location: http://chefserver.falcon.ibm.com:6443/clients/falW2k12r2x64.ammpilot.FALCON.release.ibm.com
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_response
DEBUG: Content-Length validated correctly.
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
INFO: HTTP Request Returned 409 Conflict: Client already exists
Restoring clients from /media/ibm/backup/my_backup/clients/falRhel6x64.ammpilot.FALCON.release.ibm.com.json
WARNING: client[falW2k12r2x64.ammpilot.FALCON.release.ibm.com] already exists; skipping
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_request
DEBUG: Signing the request as admin
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_request
DEBUG: Initiating POST to https://chefserver.falcon.ibm.com:6443/clients
DEBUG: ---- HTTP Request Header Data: ----
DEBUG: Content-Type: application/json
DEBUG: Accept: application/json
DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
DEBUG: X-OPS-USERID: admin
DEBUG: X-OPS-TIMESTAMP: 2016-06-16T11:10:16Z
DEBUG: X-OPS-CONTENT-HASH: TFS38qgJ3qypVPNg5p0cAHe/gU4=
DEBUG: X-OPS-AUTHORIZATION-1: csY56t1OOfBSmqWizqp7DkZzl72kLUIc5rfbR4FHqkeKIkT5mPfUaBuuha4j
DEBUG: X-OPS-AUTHORIZATION-2: P6PePunTQ9lyUvuEN8LPJri8GKi9PcRcngg+apSCvz4EjTm+iJlIMV52aoOO
DEBUG: X-OPS-AUTHORIZATION-3: W9KuEeAD1bRlP6FG1/VDMyaTU4ddMH6EQscBO8FFWxOexp38EOzzDkiY+me+
DEBUG: X-OPS-AUTHORIZATION-4: PYoMzimB8waiZM5HR8ahZIHZOoHyTnlI40ItYCfvX+ZEc+X3fvD9RYTk/G9j
DEBUG: X-OPS-AUTHORIZATION-5: B5gHgmLBkBeSyfRhFnd4QGNrpLE8RvrniABvplNzLDz36uEKI974SgoxuAQz
DEBUG: X-OPS-AUTHORIZATION-6: xdU5Ocix9YYcMpBIh2BRZtX87i+vN8QvsVzVaE5VUQ==
DEBUG: HOST: chefserver.falcon.ibm.com:6443
DEBUG: X-REMOTE-REQUEST-ID: 93922054-009b-4733-a14c-64d80f32d40b
DEBUG: Content-Length: 562
DEBUG: ---- End HTTP Request Header Data ----
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 409 Conflict
DEBUG: server: nginx/1.4.4
DEBUG: date: Thu, 16 Jun 2016 11:10:16 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 35
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.4.1
DEBUG: location: http://chefserver.falcon.ibm.com:6443/clients/falRhel6x64.ammpilot.FALCON.release.ibm.com
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_response
DEBUG: Content-Length validated correctly.
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
INFO: HTTP Request Returned 409 Conflict: Client already exists
Restoring clients from /media/ibm/backup/my_backup/clients/falRhel7x64.ammpilot.FALCON.release.ibm.com.json
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_request
DEBUG: Signing the request as admin
WARNING: client[falRhel6x64.ammpilot.FALCON.release.ibm.com] already exists; skipping
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_request
DEBUG: Initiating POST to https://chefserver.falcon.ibm.com:6443/clients
DEBUG: ---- HTTP Request Header Data: ----
DEBUG: Content-Type: application/json
DEBUG: Accept: application/json
DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
DEBUG: X-OPS-USERID: admin
DEBUG: X-OPS-TIMESTAMP: 2016-06-16T11:10:16Z
DEBUG: X-OPS-CONTENT-HASH: tNa3oh2+UzWJlH2FDFfJ1vkRGeQ=
DEBUG: X-OPS-AUTHORIZATION-1: WTm/jHWqQWIh94QS2QnsYxrc1tT2G3cZq6ndXrTe2lfDta5d+DaF5h7eKnnU
DEBUG: X-OPS-AUTHORIZATION-2: MOAGSN+voqo5nHxz8sv0U/sVBdifN7Dzwqa6cmGWNoLZfP6M9jLGzsw+99at
DEBUG: X-OPS-AUTHORIZATION-3: NBpudT6hezfTK3k9UjuiBzIbGCjcf4ew8ybXzfEi55THydeTAbYv5A6Ppru1
DEBUG: X-OPS-AUTHORIZATION-4: 6THd+iLrP8Sb3ASlZchbq66Afuf+omykgefkLmsb4dypT4YVo4m2BifTbDke
DEBUG: X-OPS-AUTHORIZATION-5: cFj26jfmqUONSshibCUJ11SgfNgRvNFROeEiwNPnYVi0wiGIulYgV51HFTXT
DEBUG: X-OPS-AUTHORIZATION-6: ofGBMm7WROVx4a+nmavglWOiJZgYqILrvd0LNHO8YQ==
DEBUG: HOST: chefserver.falcon.ibm.com:6443
DEBUG: X-REMOTE-REQUEST-ID: 93922054-009b-4733-a14c-64d80f32d40b
DEBUG: Content-Length: 562
DEBUG: ---- End HTTP Request Header Data ----
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 409 Conflict
DEBUG: server: nginx/1.4.4
DEBUG: date: Thu, 16 Jun 2016 11:10:16 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 35
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.4.1
DEBUG: location: http://chefserver.falcon.ibm.com:6443/clients/falRhel7x64.ammpilot.FALCON.release.ibm.com
DEBUG: ---- End HTTP Status/Header Data ----
WARNING: client[falRhel7x64.ammpilot.FALCON.release.ibm.com] already exists; skipping
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_response
DEBUG: Content-Length validated correctly.
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
INFO: HTTP Request Returned 409 Conflict: Client already exists
Restoring clients from /media/ibm/backup/my_backup/clients/falW2k8r2x64.ammpilot.FALCON.release.ibm.com.json
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_request
DEBUG: Signing the request as admin
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_request
DEBUG: Initiating POST to https://chefserver.falcon.ibm.com:6443/clients
DEBUG: ---- HTTP Request Header Data: ----
DEBUG: Content-Type: application/json
DEBUG: Accept: application/json
DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
DEBUG: X-OPS-USERID: admin
DEBUG: X-OPS-TIMESTAMP: 2016-06-16T11:10:16Z
DEBUG: X-OPS-CONTENT-HASH: IGYeJNPalUxOhNH2XX0lfaw8Pmw=
DEBUG: X-OPS-AUTHORIZATION-1: ZUiavFCVmOzXxiJY1OR+LPT1GQLqgq0hu1vZ9PTzanBLedlYolTRjiadalQh
DEBUG: X-OPS-AUTHORIZATION-2: p6Nv/Vwp0+PaSsW9wuzmx7C0AERHDIJfJc+3W4J4aFKV1JZh1rcn5r0Bg858
DEBUG: X-OPS-AUTHORIZATION-3: /aGxx+Smh8Q/bBQq2MAvb5isIvLYLFM/S5JoVAlYynX2jkpp/rezvvDOCegt
DEBUG: X-OPS-AUTHORIZATION-4: i6CQsQvPA62wIXNHtHP69Ahxh/aO5a/RRCrdHLyQGDcei2oatybReDeiXl8j
DEBUG: X-OPS-AUTHORIZATION-5: MqfWtdRQqtzR6meBfK3WC1pDJOv6cIbsPOd+V2ucyGyyrFOJ3inJYfGjZkEJ
DEBUG: X-OPS-AUTHORIZATION-6: kJggG8Dk0TovhYiQC6LE3hqCrJJoUQ9k7kYlsE4X8w==
DEBUG: HOST: chefserver.falcon.ibm.com:6443
DEBUG: X-REMOTE-REQUEST-ID: 93922054-009b-4733-a14c-64d80f32d40b
DEBUG: Content-Length: 563
DEBUG: ---- End HTTP Request Header Data ----
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 409 Conflict
DEBUG: server: nginx/1.4.4
DEBUG: date: Thu, 16 Jun 2016 11:10:16 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 35
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.4.1
DEBUG: location: http://chefserver.falcon.ibm.com:6443/clients/falW2k8r2x64.ammpilot.FALCON.release.ibm.com
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_response
DEBUG: Content-Length validated correctly.
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
INFO: HTTP Request Returned 409 Conflict: Client already exists
Restoring clients from /media/ibm/backup/my_backup/clients/pilotcl4.falcon.ibm.com.json
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_request
DEBUG: Signing the request as admin
WARNING: client[falW2k8r2x64.ammpilot.FALCON.release.ibm.com] already exists; skipping
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_request
DEBUG: Initiating POST to https://chefserver.falcon.ibm.com:6443/clients
DEBUG: ---- HTTP Request Header Data: ----
DEBUG: Content-Type: application/json
DEBUG: Accept: application/json
DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
DEBUG: X-OPS-USERID: admin
DEBUG: X-OPS-TIMESTAMP: 2016-06-16T11:10:16Z
DEBUG: X-OPS-CONTENT-HASH: QgajOmBkJkWE9gphaLxs26H09CI=
DEBUG: X-OPS-AUTHORIZATION-1: JJDeTdeYZFeFejyKXzcB3bEChfU9yqlRfrZIeEqMHMM0ghvvNYM3y9rCVCuU
DEBUG: X-OPS-AUTHORIZATION-2: if7tL9zg48SPLe15JrDZWtyNphgN26x4lu4XJqiblH+k2/XrhwOuLXLJsRUl
DEBUG: X-OPS-AUTHORIZATION-3: folzByU7TqK6OQId4PvtEXF+U0qCgbO0Um3p67JukVlxsR13DTgUjkSyeoW9
DEBUG: X-OPS-AUTHORIZATION-4: Ie0hbBbmSAaVmvP5fvvwkumzhgoK7p1p9zCWLwgF+zWO+iu35HNvrxQ7LGl+
DEBUG: X-OPS-AUTHORIZATION-5: X4FyvBQR6A/w4iDpY9YhnyIfNObdO1ZS2BjJb7WX/L7nzjg/S4jhPJIdTW9+
DEBUG: X-OPS-AUTHORIZATION-6: mJKeFtm4wGsZh2F93n9IjukzbJBATVuuZgeDJ2wcPQ==
DEBUG: HOST: chefserver.falcon.ibm.com:6443
DEBUG: X-REMOTE-REQUEST-ID: 93922054-009b-4733-a14c-64d80f32d40b
DEBUG: Content-Length: 542
DEBUG: ---- End HTTP Request Header Data ----
WARNING: client[pilotcl4.falcon.ibm.com] already exists; skipping
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 409 Conflict
DEBUG: server: nginx/1.4.4
DEBUG: date: Thu, 16 Jun 2016 11:10:16 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 35
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.4.1
DEBUG: location: http://chefserver.falcon.ibm.com:6443/clients/pilotcl4.falcon.ibm.com
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_response
DEBUG: Content-Length validated correctly.
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
INFO: HTTP Request Returned 409 Conflict: Client already exists
Restoring clients from /media/ibm/backup/my_backup/clients/pilotcl3.falcon.ibm.com.json
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_request
DEBUG: Signing the request as admin
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_request
DEBUG: Initiating POST to https://chefserver.falcon.ibm.com:6443/clients
DEBUG: ---- HTTP Request Header Data: ----
DEBUG: Content-Type: application/json
DEBUG: Accept: application/json
DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
DEBUG: X-OPS-USERID: admin
DEBUG: X-OPS-TIMESTAMP: 2016-06-16T11:10:16Z
DEBUG: X-OPS-CONTENT-HASH: A56FM9afuHdEAmGRgXEkjkv6suU=
DEBUG: X-OPS-AUTHORIZATION-1: ytuMxN4excnSB7jBDSUJpff3rpHt/VZAHif4TfX8+OPhislj+NdI1jDpcy2Z
DEBUG: X-OPS-AUTHORIZATION-2: z5/V/itQrCgQ4wtSI2ooZLSzS5zAxlYn/ngskftTRbTm7EP3pC9Hbs/+UZnd
DEBUG: X-OPS-AUTHORIZATION-3: U4lAOvfBqp7ZgRx8FhubuPdaZL/MM8fh0/Dpc2TE67QkWjwC08GJ9iIUbrPt
DEBUG: X-OPS-AUTHORIZATION-4: ly7gtd7DMbx3/tja8ChwCZ1o8Z+whRNHFajPvg6tIX0rg7/LLFEyEW+OpMTA
DEBUG: X-OPS-AUTHORIZATION-5: fMk8DFNXt3qm4cNHYulwYtePgN0eVq8b8Z/GQlsRVTFkFdJ+g4eg6RWvfoQ7
DEBUG: X-OPS-AUTHORIZATION-6: P/GbAP59caqGv7AzyalV6+GkuQSMQ+VjxXRUqcx+9A==
DEBUG: HOST: chefserver.falcon.ibm.com:6443
DEBUG: X-REMOTE-REQUEST-ID: 93922054-009b-4733-a14c-64d80f32d40b
DEBUG: Content-Length: 542
DEBUG: ---- End HTTP Request Header Data ----
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 409 Conflict
DEBUG: server: nginx/1.4.4
DEBUG: date: Thu, 16 Jun 2016 11:10:16 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 35
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.4.1
DEBUG: location: http://chefserver.falcon.ibm.com:6443/clients/pilotcl3.falcon.ibm.com
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_response
DEBUG: Content-Length validated correctly.
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
WARNING: client[pilotcl3.falcon.ibm.com] already exists; skipping
INFO: HTTP Request Returned 409 Conflict: Client already exists
Restoring clients from /media/ibm/backup/my_backup/clients/chef-validator.json
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_request
DEBUG: Signing the request as admin
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_request
DEBUG: Initiating POST to https://chefserver.falcon.ibm.com:6443/clients
DEBUG: ---- HTTP Request Header Data: ----
DEBUG: Content-Type: application/json
DEBUG: Accept: application/json
DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
DEBUG: X-OPS-USERID: admin
DEBUG: X-OPS-TIMESTAMP: 2016-06-16T11:10:16Z
DEBUG: X-OPS-CONTENT-HASH: qvHXzT71CAnm+A+X+oA9qWLG8uE=
DEBUG: X-OPS-AUTHORIZATION-1: Swq3Y74+3sIQ6tdaKPXf/w0JnvxigXpHEg0dnzqWc70WejuHh+XH9ESJMfRi
DEBUG: X-OPS-AUTHORIZATION-2: 6bGqoO+TjvJ+O36+5K2DURXjDfcdMSw8ccmc/scASPaEZfFyefc8stBq1nqz
DEBUG: X-OPS-AUTHORIZATION-3: uGK9xgmsTCiYCZa42c7DWYTPpBCJOolTolrJH8LBZEFwdPLUoltsyEkwwZ9O
DEBUG: X-OPS-AUTHORIZATION-4: dOV7qX0iUjZzZyB2teAMcw+JiFrbIvoyfBF/Y/LPD3LQx73b6QSVQnvwOh19
DEBUG: X-OPS-AUTHORIZATION-5: i0LY7LpDvpljNymxn9AzR+u1kSNruPPmsE4bvZnqsQng1SUwJVT07zoXHnsv
DEBUG: X-OPS-AUTHORIZATION-6: fBvGP/b4GME0OGJ1yOBUeeVuSVAl7CTbWdnjK7Y5UA==
DEBUG: HOST: chefserver.falcon.ibm.com:6443
DEBUG: X-REMOTE-REQUEST-ID: 93922054-009b-4733-a14c-64d80f32d40b
DEBUG: Content-Length: 532
DEBUG: ---- End HTTP Request Header Data ----
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 409 Conflict
DEBUG: server: nginx/1.4.4
DEBUG: date: Thu, 16 Jun 2016 11:10:16 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 35
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.4.1
DEBUG: location: http://chefserver.falcon.ibm.com:6443/clients/chef-validator
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_response
DEBUG: Content-Length validated correctly.
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
WARNING: client[chef-validator] already exists; skipping
INFO: HTTP Request Returned 409 Conflict: Client already exists
=== Restoring users ===
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_request
DEBUG: Signing the request as admin
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_request
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_request
DEBUG: Initiating POST to https://chefserver.falcon.ibm.com:6443/users
DEBUG: ---- HTTP Request Header Data: ----
DEBUG: Content-Type: application/json
DEBUG: Accept: application/json
DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
DEBUG: X-OPS-USERID: admin
DEBUG: X-OPS-TIMESTAMP: 2016-06-16T11:10:16Z
DEBUG: X-OPS-CONTENT-HASH: QkDu0j8zD17OFSeIAYHUSTWRgno=
DEBUG: X-OPS-AUTHORIZATION-1: snG7UrIKIs2w62cR1dW6IghnlEAsapBuDYKFhYZMfCpFFnj7DPWFzSAEsoVX
DEBUG: X-OPS-AUTHORIZATION-2: 0kwqHcvweXDDYcmo9iFglOCRdGP2Uh0pl0fbLGbvUUHzXi7TEF7IdYPSTbdd
DEBUG: X-OPS-AUTHORIZATION-3: F95pRmBSoasQrzsEk0BLnuubFnRyYxs1+v7Y0cga1qZHq+Gdc/0E29FvAGo8
DEBUG: X-OPS-AUTHORIZATION-4: Kn5YAVqTluGQRCxmRhwfmZogcrC6yTwI8lXPAFGEoBOY0ZLm5J/DjjXs15vz
DEBUG: X-OPS-AUTHORIZATION-5: BWfWtIN3UKf2DnvTEDm4+SoYVS0j/v4QC7uM4DDlHkhdCeyZz078zOdtXdJB
DEBUG: X-OPS-AUTHORIZATION-6: OwDe7LlgxFqUUkzjhooVoyAMUSj/vdVz0EAvMQM9sQ==
DEBUG: HOST: chefserver.falcon.ibm.com:6443
DEBUG: X-REMOTE-REQUEST-ID: 93922054-009b-4733-a14c-64d80f32d40b
DEBUG: Content-Length: 527
DEBUG: ---- End HTTP Request Header Data ----
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 409 Conflict
DEBUG: server: nginx/1.4.4
DEBUG: date: Thu, 16 Jun 2016 11:10:17 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 41
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.4.1
DEBUG: location: http://chefserver.falcon.ibm.com:6443/users/admin
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_response
DEBUG: Content-Length validated correctly.
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
INFO: HTTP Request Returned 409 Conflict: User 'admin' already exists
WARNING: user[admin] already exists; skipping
=== Restoring nodes ===
Restoring nodes from /media/ibm/backup/my_backup/nodes/Pilot-test-2.falcon.ibm.com.json
/opt/chef/embedded/apps/chef/lib/chef/node.rb:464:in json_create': undefined methodeach' for nil:NilClass (NoMethodError)
from /opt/chef/embedded/apps/chef/lib/chef/knife/core/object_loader.rb:94:in object_from_file' from /opt/chef/embedded/apps/chef/lib/chef/knife/core/object_loader.rb:44:inload_from'
from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-backup-0.0.12/lib/chef/knife/backup_restore.rb:118:in block in restore_standard' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-backup-0.0.12/lib/chef/knife/backup_restore.rb:116:ineach'
from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-backup-0.0.12/lib/chef/knife/backup_restore.rb:116:in restore_standard' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-backup-0.0.12/lib/chef/knife/backup_restore.rb:75:innodes'
from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-backup-0.0.12/lib/chef/knife/backup_restore.rb:60:in block in run' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-backup-0.0.12/lib/chef/knife/backup_restore.rb:60:ineach'
from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-backup-0.0.12/lib/chef/knife/backup_restore.rb:60:in run' from /opt/chef/embedded/apps/chef/lib/chef/knife.rb:493:inrun_with_pretty_exceptions'
from /opt/chef/embedded/apps/chef/lib/chef/knife.rb:174:in run' from /opt/chef/embedded/apps/chef/lib/chef/application/knife.rb:139:inrun'
from /opt/chef/embedded/apps/chef/bin/knife:25:in <top (required)>' from /usr/bin/knife:38:inload'
from /usr/bin/knife:38:in `

Let me know if you need to have copy of the backup export whole directory.

knife plugin version : 0.0.12
chef server version : 11.18.12