What happens if you reboot the box?  I haven't tried this myself but I've 
seen windows delay applying updates until shutdown (and I think following a 
reboot too in some cases).

Might need a bit of work judging by the comments but there is a win_reboot 
module which you could try.
https://github.com/ansible/ansible/pull/8946/files

Jon

On Thursday, March 26, 2015 at 7:16:01 PM UTC, Dimitri Yioulos wrote:
>
> Hi, Jon.
>
> I appreciate the response, and certainly will look into your suggestions.  
> I'm using version 1.8.4.
>
> As I've continued to hack away, I've got this to work, kind of:
>
> ansible somehost -m win_updates -a category:security
>
> The output looks like this:
>
> somehostb | success >> {
>     "changed": true, 
>     "updates_already_present": [
>         "2506014", 
>         "2506212", 
>         "2511455", 
>         "2509553", 
>         "2506928",
>               ~
>     "updates_category": "critical", 
>     "updates_installed": [], 
>     "updates_installed_afterwards": [
>         "2506014", 
>         "2506212", 
>         "2511455", 
>         "2509553", 
>         "2506928", 
>               ~
>     "updates_installed_count": 0, 
>     "updates_reboot_needed": true, 
>     "updates_success": "true"
> }
>
> The curious thing is that no updates are made, despite the fact that 
> updates are available on the Win server, and they are of the category 
> "Security", as in the following:
>
> Security Update for Windows Server 2008 R2 x64 Edition (KB3002657)
> Download size: 1.3 MB
> You may need to restart your computer for this update to take effect.
> Update type: Important
>
> That comes from the Windows Update Manager.  I tried changing 
> "Category:security" to "Category:important", and still no joy.
>
> Ideas?
>
>
> On Thursday, March 26, 2015 at 10:27:10 AM UTC-4, Dimitri Yioulos wrote:
>>
>> All,
>>
>> I've got Ansible working on a few Windows 2008 servers.  The Ansible 
>> command server runs CentOS 6.  I'm trying to get the module "win_updates" 
>> working, but am not having much success.  I'd like to be able to run this 
>> both via the command line, and via a playbook.  The extant documentation 
>> isn't very detailed.  Here's what I've done/am trying (sorry, this will 
>> probably be long):
>>
>> * I had to download the windows module of which win_updates is a part, 
>> and manually put it in 
>> "/usr/lib/python2.6/site-packages/ansible/modules/extras/"
>> * I installed "PSWindowsUpdate" on the Windows server
>> * If I run the command "ansible myhost -m win_updates", I get the 
>> following output:
>>
>> myhost | success >> {
>>     "changed": false, 
>>     "updates_already_present": null, 
>>     "updates_category": "critical", 
>>     "updates_installed": [], 
>>     "updates_installed_afterwards": null, 
>>     "updates_installed_count": 0, 
>>     "updates_reboot_needed": true, 
>>     "updates_success": "true"
>> }
>>
>> Fine, but the updates aren't done.  So, I figure I need an argument.  The 
>> win_updates document gives the following example:
>>
>> # Install updates from security category
>> win_updates:
>>   category: security
>>
>> I've tried every combination I can think of, as in:
>>
>> "ansible myhost -m win_updates -a category=security" and  "ansible myhost -m 
>> win_updates -a security" and "ansible myhost -m win_updates -a 
>> category:security", and I get something like this:
>>
>> myhost | FAILED >> {
>>     "failed": true, 
>>     "msg": "\nProcess is terminated due to StackOverflowException.\n", 
>>     "parsed": false
>> }
>>
>> * I created the following playbook:
>>
>> ---
>>
>> - name: update windows
>>   hosts: windows
>>   gather_facts: true
>>   tasks:
>>     - name: win update
>>       win_updates:
>>         category: security
>>
>> It, too, fails, with a much more verbose error message (which I'll skip 
>> posting, for now).  I've tried other combinations in the playbook and, they 
>> too, fail.
>>
>> I would greatly appreciate help in getting this to work, both from the 
>> command line and from a playbook.
>>
>> Dimitri
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/1109a545-2032-4f69-adb1-5e1261d041a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to