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!!
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.
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.
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.
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?
Most likely multiple unsuccessful deployments without proper cleanup.
@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?
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.
Hi @alexal,
good point, interesting. That is why the rpm command.
Perhaps this could be added to the documentation, as troubleshooting points?
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 16. Read more here about why you should contribute and what is in it for you!