[chef] Re: Re: window_reboot attribute issue

["David A. Williams" < >]

Right. To Julian's point, this is before my other entries.

include_recipe 'windows::reboot_handler'


David

On 5/12/14 9:45 AM, "David A. Williams" 
<
 >
 wrote:

>Please ignore what is in the EOH block.  It is suppose to be 3 dots but it
>got lost in translation.
>
>
>David
>
>On 5/12/14 9:39 AM, "David A. Williams" 
><
 >
> wrote:
>
>>Premkumar,
>>
>>I set mine up like this.
>>
>>windows_reboot 60 do
>>   reason 'Opscode Chef initiated reboot'
>>   action :nothing
>>end
>>
>>Then later on, I request it from another resource
>>
>>batch "Install Microsoft #{kb.chomp('-v2')}" do
>>  code <<-EOH
>>  ?$B!&?(B€?$B%r?(B
>>  EOH
>>  notifies :request, "windows_reboot[60]"
>>end
>>
>>Reply-To: 
>>"
 <mailto:
 >"
>><
 <mailto:
 >>
>>Date: Monday, May 12, 2014 9:26 AM
>>To: 
>>"
 <mailto:
 >"
>><
 <mailto:
 >>
>>Cc: C2C CHEF 
>><
 <mailto:
 >>
>>Subject: [chef] window_reboot attribute issue
>>
>>I want to install and upgrade HPsitescope package for that reboot need
>>after installing the package.
>>
>>I tried to use window_reboot attribute but rebooting of the windows box
>>is not happening. Whether I missed something on the code ?
>>
>>
>>catdefault.rb
>>
>>windows_reboot 0 do
>>action:request
>>timeout 0
>>end
>>
>>
>>PS C:\Users\a427665\chef\cookbooks\HPSiteScope> chef-solo -c solo.rb -j
>>solo.json -l debug -L log.txt
>>c:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/windows-api-0.4.0/lib/w
>>i
>>ndows/api.rb:4: Use RbConfig instead of obsole
>>te and deprecated Config.
>>Starting Chef Client, version 11.6.2?$B"+?(B[0m
>>Compiling Cookbooks...?$B"+?(B[0m
>>Recipe: windows::default?$B"+?(B[0m
>>  * chef_gem[win32-api] action install?$B"+?(B[0m (up to date)?$B"+?(B[0m
>>  * chef_gem[win32-service] action install?$B"+?(B[0m (up to
>>date)?$B"+?(B[0m
>>  * chef_gem[windows-api] action install?$B"+?(B[0m (up to
>>date)?$B"+?(B[0m
>>  * chef_gem[windows-pr] action install?$B"+?(B[0m (up to
>>date)?$B"+?(B[0m
>>  * chef_gem[win32-dir] action install?$B"+?(B[0m (up to date)?$B"+?(B[0m
>>  * chef_gem[win32-event] action install?$B"+?(B[0m (up to
>>date)?$B"+?(B[0m
>>  * chef_gem[win32-mutex] action install?$B"+?(B[0m (up to
>>date)?$B"+?(B[0m
>>Converging 8 resources?$B"+?(B[0m
>>  * chef_gem[win32-api] action install?$B"+?(B[0m (up to date)?$B"+?(B[0m
>>  * chef_gem[win32-service] action install?$B"+?(B[0m (up to
>>date)?$B"+?(B[0m
>>  * chef_gem[windows-api] action install?$B"+?(B[0m (up to
>>date)?$B"+?(B[0m
>>  * chef_gem[windows-pr] action install?$B"+?(B[0m (up to
>>date)?$B"+?(B[0m
>>  * chef_gem[win32-dir] action install?$B"+?(B[0m (up to date)?$B"+?(B[0m
>>  * chef_gem[win32-event] action install?$B"+?(B[0m (up to
>>date)?$B"+?(B[0m
>>  * chef_gem[win32-mutex] action install?$B"+?(B[0m (up to
>>date)?$B"+?(B[0m
>>Recipe: HPSiteScope::default?$B"+?(B[0m
>>  * windows_reboot[0] action request?$B"+?(B[0m (up to date)?$B"+?(B[0m
>>Chef Client finished, 0 resources updated?$B"+?(B[0m
>>PS C:\Users\a427665\chef\cookbooks\HPSiteScope>
>>
>>
>>Any cookbooks are available for HPsitescope package installation on
>>window ?
>>
>>
>>Thanks & Regards,
>>Premkumar
>>UTS
>>
>>
>>________________________________
>>CONFIDENTIALITY NOTICE: This electronic mail may contain information that
>>is privileged, confidential, and/or otherwise protected from disclosure
>>to anyone other than its intended recipient(s). Any dissemination or use
>>of this electronic mail or its contents by persons other than the
>>intended recipient(s) is strictly prohibited. If you have received this
>>communication in error, please notify the sender immediately by reply
>>e-mail so that we may correct our internal records. Please then delete
>>the original message. Thank you.
>


CONFIDENTIALITY NOTICE:  This electronic mail may contain information that is 
privileged, confidential, and/or otherwise protected from disclosure to 
anyone other than its intended recipient(s).  Any dissemination or use of 
this electronic mail or its contents by persons other than the intended 
recipient(s) is strictly prohibited.  If you have received this communication 
in error, please notify the sender immediately by reply e-mail so that we may 
correct our internal records.  Please then delete the original message.  
Thank you.