/opt/sas/viya/config/etc/sysconfig/sas-javaesntl/sas-java does not exist !

[AmitSri]

Hi,

I am upgrading sas viya from 3.2 to 3.3 and I am getting this error as:

fatal: [deployTarget]: FAILED! => {"changed": false, "failed": true, "msg": "Destination /opt/sas/viya/config/etc/sysconfig/sas-javaesntl/sas-java does not exist !", "rc": 257}

But, I had set the sas_install_java= true in the vars.yml and Java is getting installed as well. But, still the deployment is failing. Does any one can help on this?

Thanks!!

[alexal]

@AmitSri,

This is the first upgrade attempt? If not, how was the cleanup performed between them? Please run this command and show me the output:

$ ansible -i inventory.ini all -m shell -a 'rpm -vV sas-javaesntl'

If you deleted / moved / remounted /opt/sas/viya without uninstalling the packages, Ansible won't attempt to reinstall them because it thinks they're already installed.

[AmitSri]

Hi Alex, I had run ansible-playbook deploy-cleanup.yml before installing it.

Please find the output that you asked for:
[root@gspdsv04 sas_viya_playbook]# ansible -i inventory.ini all -m shell -a 'rpm -vV sas-javaesntl'
[WARNING]: Consider using yum, dnf or zypper module rather than running rpm

deployTarget | FAILED | rc=1 >>
......... /etc/sysconfig/sas/sas-java-services-viya
......... /etc/sysconfig/sas/sas-java-viya
missing /opt/sas/viya/config/etc/sysconfig/sas-javaesntl
missing c /opt/sas/viya/config/etc/sysconfig/sas-javaesntl/sas-java
missing c /opt/sas/viya/config/etc/sysconfig/sas-javaesntl/sas-java-services
Thanks!!

[alexal · Accepted solution]

@AmitSri,

Run this command:

ansible -i inventory.ini all -m shell -a 'sudo rpm -e sas-javaesntl'

After that run deploy-cleanup.yml  and try to install SAS Viya 3.3 once again.

[JuanS_OCS]

Thank you @alexal. This helped me for one specific installation.

Do you have an idea of why or how does this error is generated, in the first, place?

[alexal]

@JuanS_OCS,

Most likely multiple unsuccessful deployments without proper cleanup.

[JuanS_OCS]

@alexal, interesting, because it is true the part of the "multiple unsuccessful deployments" but, and exactly my point, I would like to go through the part of "without proper cleanup".

Before any deployment attempt, always execute the deploy-cleanup.yml before and after killing the ps -ef | grep viya processes. Also according to docunmentation. And, still, got this error once.

What would it be a proper cleanup? Could you please share your steps to ensure cleanups?

[alexal]

@JuanS_OCS,

Based on my experience in addition to deploy-clenup.yml you always need to use YUM to check for missing SAS packages. Most likely there will be some. We've already reported that to R&D and they made some changes the will improve a cleanup process in the future versions.

[JuanS_OCS]

Hi @alexal,

good point, interesting. That is why the rpm command. 

Perhaps this could be added to the documentation, as troubleshooting points?

[AmitSri]

Hi Alex,

Thank you so much. This made my deployment successfully. Viya is now upgraded to 3.3. Thanks again!!

[alexal]

@AmitSri,

You are welcome! I'm glad the problem has been resolved.