Works when run manually.
Even with ansible, when we run the playbook the setup.exe is running but it’s 0% CPU and
I am not sure typically how long it would take for the installation would complete but hours on end it’s just running on ansible.
Can someone please help? The system still gets stuck with setup.exe at 0 % CPU and keeps the installation of Oracle 12 c running.
but it’s not moving forward at all.
Make sure that you have removed ALL Oracle-related environment variables and try it again manually. I reckon there is something that is NOT in the response file, but that is supplied via another channel such as an environment variable when you do it manually.
It definitely sounds as if the setup is waiting for manual input.
I have tried it several times manually with proper cleanup and it has worked everyone with this answer file. What I see while installing through Ansible is it starts the setup.exe but the other screen of command line Oracle universal installer doesn’t pop up during installation through Ansible. Is there anyway I can set this up for Ansible? I am new to Ansible, please help.
Thanks for the quick reply. I see Oracle universal installer window open up when I run this manually through power shell or command line. I didn’t see either anything popping up while installing through sensible nor is the installation moving forward. No app folder is created or setup.exe also does not use any CPUs i am using -waitforcompletion switch and -ignoreSysPrereqs switch as well apart from -silent and responsefile
I have just tried it locally and manually and it works every time. I just created a couple of new Windows servers and installing it with ansible hangs again so it does not seem to be a cleanup issue.
If you can run it remotely from another windows vm you should be able to see where it breaks side-by-side. Also, is there a reason you’re not using win_package?
For msi and exe packages - use win_package as a rule of thumb. If you still have issues with these, you can report an issue here https://github.com/ansible/ansible/issues because the module’s supported by the community.
win_command shouldn’t be used for installations as it usually ends up in a hit or a miss situation. If win_package doesn’t work for you, you can try putting your win_command arguments as a pwsh script, saving it on the target node, and running that script through a remote powershell session. If you don’t know how to do that, you can look up invoke-command or new-pssession. Ansible uses winrm as well so any issues you have with ansible should be visible by running this script remotely.
It’s very hard for us to help you in this situation but basically it boils down to you running these checks and finding out what is causing the program to hang;
Use something like procexp to see if the setup.exe process is spawning any child processes that are running in the background
Ensure your quoting is not screwing up the install process, in your first example you have quoted the responseFile path arg but you don’t need this quoted.
Try and replicate this through another WinRM session like PowerShell’s Invoke-Command or Enter-PSSession
Use Ansible become on the task to escape the boundary of the WinRM logon and run through a psuedo-interactive process
See if there is any logging you can enable on the Oracle installer, this could tell you the stage it is up to and what it may be waiting on
As for why you cannot see it when running through Ansible, Ansible uses a completely separate session to run your processes as any normal interactive logon. This is not unique to Ansible but how Windows treats things like network logons such as WinRM.
In addition to Jordan’s recommendations, have you created an oraInventory? I haven’t automated the OUI on Windows but generally, on *nix platforms you need to manually create an empty OUI inventory with the appropriate ownerships and permissions. (You can work this out from a successful install but on a Linux-based host it would be similar to:
Hi,
Thanks for the replies.
I have the same issues with the with remote powershell.
I still see 0% CPU utilization. I am not sure how to move forward. I am still seeing the same issues.