Note: Please go to to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > FAQs > Why am I getting a warning that following cookbooks are present but do not satisfy all version requirements?

Why am I getting a warning that following cookbooks are present but do not satisfy all version requirements?

Table of Contents


When using Chef cookbooks in your ServerTemplates, you may see a warning indicating that cookbooks are present but do not satisfy all version requirements.

  • These cookbooks do not satisfy all version requirements

Error when Launching a Server



RightScale will only show this warning when designing or launching ServerTemplates on the HEAD revision. We hide the warning on committed revisions. You will get additional warnings when launching, committing, or publishing a ServerTemplate with this condition, though RightScale won't prevent you from taking those actions.


Within the metadata of a Chef cookbook (found in the metadata.rb file), you can specify other cookbooks that this cookbook depends on to run (for more information see the Opscode documentation). When you attach a cookbook to a ServerTemplate, RightScale uses this metadata and tries to resolve all dependencies by looking for the dependent cookbooks in your account in the primary namespace. If RightScale can't find the dependent cookbooks in the primary namespace, this warning message is displayed.


Note: just because a cookbook "depends" on another cookbook doesn't necessarily mean that the dependent cookbook is required for your server to launch successfully. If the cookbook that has the dependency is never used, or its recipes never actually use resources in the dependent cookbook, your server may launch with no errors. RightScale can't parse all the code to make this determination, so we show the warning solely based on the metadata information.


If you are seeing this message, there are multiple resolution paths to consider:

  • Import the dependent cookbook into the primary namespace - by importing the dependent cookbook into your primary namespace, RightScale will be able to automatically resolve the dependency. You may have to locate the origin of the cookbook if it is not a cookbook that you have created. To do this, add the repository to your account and then import the cookbook from your repository.
  • Select the dependent cookbook from the alternate namespace - if the cookbook already exists in your account but is in the alternate namespace, you can locate it be clicking on the search icon button_SearchCookbook.png and selecting the appropriate cookbook.
  • Remove the cookbook(s) that have the dependency - if you are not actually using the cookbook(s) that call out the particular dependency, you can remove the cookbooks from the ServerTemplate by clicking the close icon button_CookbookClose.png next to the name of the cookbook. Note: we currently don't have a way of showing you which cookbooks are causing the dependency errors. If that is a feature that would be useful to you, please let us know on our feedback forum.
  • Do nothing - If the dependency isn't really required by the specific resources/recipes that you are using in the ServerTemplate, you can do nothing and RightScale will not prevent you from launching or committing the ServerTemplate (though we will warn you again before completing the action).
You must to post a comment.
Last modified
14:50, 30 Sep 2013



This page has no classifications.



© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.