Error: Timeout (12s) waiting for privilege escalation prompt in SAS Viya 3.3 install

[Asif4862]

Hi All,

I've only one error during installation and configuration of SAS Viya 3.3. Please let me know what is the issue/problem from my end.

The error msg is: Timeout (12s) waiting for privilege escalation prompt
i.e:

TASK [framework : Verify the presence of the desired artifact] *****************
fatal: [deployTarget]: FAILED! => {"failed": true, "msg": "Timeout (12s) waiting for privilege escalation prompt: "}

PLAY RECAP *********************************************************************
deployTarget : ok=1935 changed=474 unreachable=0 failed=1
localhost : ok=10 changed=1 unreachable=0 failed=0

Attached is the error screenshot

Thanks
Asif

[alexal]

@Asif4862,

What version of Ansible are you using?

[Asif4862]

I'm using ansible version 2.3.2.0

More details are given below:
ansible 2.3.2.0
config file = /sas/install/sas_viya_playbook/ansible.cfg
configured module search path = [u'./library']
python version = 2.6.6 (r266:84292, Aug 9 2016, 06:11:56) [GCC 4.4.7 20120313 (Red Hat 4.4.7-17)]

[alexal]

That should work. Did you try to increase timeout value in ansible.cfg?

[Asif4862 · Accepted solution]

Thanks Alexal, I found a resolution step in SAS Viya 3.3 Deployment Guide and I'm able to resolve that issue.
Resolution steps are:
TimeoutError(error_message)TimeoutError
Error
When running the deployment:
TimeoutError(error_message)\nTimeoutError:
Timer expired\n", "rc": 257} 13:15:37 |
INFO: | * 13:15:37 |
WARNING: | Execution return code '2'
is not the expected value '0' 13:15:37 |
INFO: | * 13:15:37 |
INFO: | Updating deployment times data
for step deploy_time with value 19 13:15:37 |
INFO: | * 13:15:37 |
WARNING: | Ansible execution
encountered failures
Explanation
The system failed to gather mount information.
Resolution
Perform one of the following actions:
n
Set /etc/mtab as a link to /proc/mounts by running the following command:
sudo ln -s /proc/mounts /etc/mtab
n
Edit the ansible.cfg file and add or change the time-out value for Ansible as follows:
timeout=number-of-seconds
Deploy your software by running the Ansible playbook again.

I increases the timeout value to 300 and able to resolved that issue.

Thanks for your help!!!

[alexal]

@Asif4862,

You are welcome!