Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with #25

Closed
kPhilosopher opened this issue Jul 10, 2013 · 9 comments
Closed

Issue with #25

kPhilosopher opened this issue Jul 10, 2013 · 9 comments

Comments

@kPhilosopher
Copy link

When I use a role to define a run_list specific for an environment and pin the cookbook version, I get the following error when I execute chef-client

DEBUG: Sending HTTP Request via POST to 10.10.10.2:4000/environments/environment01/cookbook_versions
INFO: HTTP Request Returned 412 Precondition Failed: No such cookbook: cookbookName::recipeName

This seems to happen if we have a role specifying the version of the cookbook for an environment. For example:

** RECIPE COMMANDS **
{
  "name": "roleName",
  "json_class": "Chef::Role",
  "env_run_lists": {
    "environment01": [
      "recipe[cookbookName::recipeName@0.1.1]"
    ],
    "environment02": [
       "recipe[cookbookName::recipeName@0.1.0]"
  ],
  },
  "run_list": [ ],
  "description": "role applied to nodes",
  "chef_type": "role",
  "override_attributes": {
  }
}

This issue went away when we would change

"recipe[cookbookName::recipeName@0.1.1]"

to

"recipe[cookbookName::recipeName]"

Please let me know if you need more information.

@jkeiser
Copy link
Contributor

jkeiser commented Jul 10, 2013

Hmm. I think this might happen even if you specify it in the run_list itself, too.

I have a fix in master (commit 8d76496). Can you sync, rake install, and try out that version?

@sethvargo
Copy link
Contributor

@jkeiser master works for me 😄

@jkeiser
Copy link
Contributor

jkeiser commented Jul 10, 2013

@sethvargo just so I understand, did it fail before?

@sethvargo
Copy link
Contributor

@jkeiser that I don't know. I can confirm it's working on master, but I never tried before (I try not to do version locking that way, so I never encountered it)

@kPhilosopher
Copy link
Author

It works with the master (commit 8d76496). Do you have an estimate for the next version release?

@jkeiser
Copy link
Contributor

jkeiser commented Jul 11, 2013

Soon. I want to get some chef-pedant tests written for the case, but if you have a need for a new version Right Now I can release and add the chef-pedant tests after.

@kPhilosopher
Copy link
Author

It would be appreciated if you can release a patch, but I don't want to pressure you to deviate from better practices.

@jkeiser
Copy link
Contributor

jkeiser commented Jul 12, 2013

I went ahead and released 1.5.4. I still need to get tests in for this, but don't want to block anyone in the meantime.

@kPhilosopher
Copy link
Author

Thanks John.

@chef chef locked and limited conversation to collaborators Nov 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants