What does Ohai currently report the platform as?
You can get this to work by doing the following in /etc/chef/client.rb:
require 'chef/platform'
Chef::Platform.set(:platform => :WHAT_OHAI_REPORTS_FOR_PLATFORM, :resource => :service, :provider => Chef::Provider::Service::Redhat)
Chef::Platform.set(:platform => :WHAT_OHAI_REPORTS_FOR_PLATFORM, :resource => :cron, :provider => Chef::Provider::Cron)
Chef::Platform.set(:platform => :WHAT_OHAI_REPORTS_FOR_PLATFORM, :resource => :package, :provider => Chef::Provider::Package::Yum)
Chef::Platform.set(:platform => :WHAT_OHAI_REPORTS_FOR_PLATFORM, :resource => :package, :provider => Chef::Provider::Mdadm)
You could also do this in an attribute file or a cookbook library.
Best,
Adam
---
Opscode, Inc.
Adam Jacob, Chief Product Officer
T: (206) 619-7151 E: ">
On Oct 24, 2011, at 6:40 PM, Daniel DeLeo wrote:
> On Monday, October 24, 2011 at 4:49 PM, Joshua Timberman wrote:
>> Hi there!
>>
>> The root of the problem is that the tool Chef uses to detect
>> information about the node it is running on, Ohai, does not have a
>> plugin to properly detect Oracle Linux. This will affect four
>> resources:
>>
>> cron
>> mdadm
>> package
>> service
>>
>> When you have recipes that use any of these recipes, you'll probably
>> need to add the "provider" parameter to these resources so they work
>> on Oracle Linux.
>>
>> We'd like to correct the problem, though. Please open a ticket at
>> tickets.opscode.com (http://tickets.opscode.com) in the OHAI project to add support for Oracle
>> Linux. If there's an /etc/redhat-release, please include its contents
>> in the ticket.
> Once ohai knows what Oracle Linux is, Chef will need to be updated to use the yum package provider for package resources (&etc.), so please also create a ticket in the CHEF project and reference the Ohai ticket. (hint: if you write a ticket number like OHAI-123 in the description, it will auto-link).
>
> Thanks,
>
> --
> Dan DeLeo
Archive powered by MHonArc 2.6.16.