search

cerner / knife-tar

Chef gem for uploading configuration in tar files
Apache License 2.0
10 stars 3 forks source link

knife cookbook tar upload not actually uploading cookbooks #9

Open jrh3k5 opened 10 years ago

jrh3k5 commented 10 years ago

We're using the knife-tar 1.x stream with Chef 10.14.0 on the server and Chef 10.24.0 on the client. We're seeing the console allege that the cookbooks from our TAR bundle are getting uploaded:

[INFO] Uploading flume_agent    [1.0.2]
[INFO] Uploading maven_artifact [1.0.0]
[INFO] Uploading my_cookbook [5.1.0]
[INFO] Uploading splunk_forwarder [1.1.0]
[INFO] Uploaded all cookbooks.

However, we never see the updated cookbook version reflected on the Chef server.

bbaugher commented 10 years ago

Knife-tar uses the class used for knife cookbook upload ... under the covers. Can you verify your knife points to the right chef server by trying knife cookbook list?

jrh3k5 commented 10 years ago

I neglected to make it clear: this is when trying to upload uber bundles. If I try to upload a single-cookbook TAR file (i.e., a TAR ball containing only one cookbook) using the knife cookbook tar upload command, it works.

Does that affect the steps you outlined?

bbaugher commented 10 years ago

Hmm, I guess that throws out the idea that the knife config is incorrect. The message Uploading [COOKBOOK] [VERSION] actually comes from the cookbook upload class in Chef. So as long as that information (cookbooks/versions) is correct I'm not sure this is a knife-tar problem.

jrh3k5 commented 10 years ago

What puzzles me is that this only happens on multi-cookbook uploads.