You can probably workaround by using win_command or raw to run msiexec. Unfortunately there are a few .msi installers around which don't write a product id. Might be worth raising a bug on the rubyinstaller site, as its really a poorly made installer that is causing the problem here.
Jon -- 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/3a80e2c5-f4ae-43e0-acaf-d75c5013031b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
