The process of applying hot fixes to SAS Viya 3.4 and SAS Viya 3.5 is also known as updating the deployment. The full process is outlined in the documentation here:
Here is a brief summary of the process:
This SAS KB article discusses how to confirm whether you will receive updates. It also provides some troubleshooting steps.
How do I determine whether my deployment uses a mirror repository?
All SAS Viya deployments on SUSE Linux use a mirror repository, so this question applies only to deployments on other supported Linux operating systems. There are multiple ways to determine whether your deployment uses a local mirror repository or whether it receives updates directly from SAS hosted repositories, including via yum commands.
This SAS KB article focuses on the simple methods for determining this via examining the files on the SAS Viya system. Note that the machine where Ansible is executed could be a separate machine from the SAS Viya deployment. The commands below are meant to be used on the machines in the SAS Viya deployment, that is, the machines that are defined in sas_viya_playbook/inventory.ini. You could use Ansible to run these commands on multiple machines at once, if desired.
When you would use a mirror repository
Examples:
The following output indicates that the system is configured for local repositories that are located at /mnt/viya/35:
The following output indicates that the system is configured for local repositories that are served by a web server at http://myserver.example.com.
When you would not use a mirror repository
For example, the following output shows multiple /etc/yum.repos.d/sas-*yum.repo files, each with a baseurl pointing to https://ses.sas.download:
How do I update my local mirror repository?
The process of updating a local mirror repository is performed with the correct SAS® Mirror Manager tool for your Viya release:
Directions for using SAS Mirror Manager are in the deployment documentation here:
How do I verify whether I will receive updates when running the update playbook?
After you update your mirror, as described above, or you do not use a mirror and get updates directly from SAS, run the following commands on the SAS Viya machines.
Red Hat Enterprise Linux (RHEL):
SUSE Linux:
If there are available updates detected by yum or zypper, the command output lists them, as shown here:
If no package list is produced, you might have all available updates, or something has gone wrong. Take one of these steps:
Two Ansible playbooks, site.yml and update-only.yml, that can apply updates are provided with your SAS Viya order. Older SAS Viya 3.4 orders might not contain update-only.yml. In that case, simply use site.yml to update the deployment. The main difference for these playbooks is that update-only.yml performs only the tasks necessary to apply updates. The update-only.yml playbook completes more quickly than site.yml in most cases.
Why are there no updates available?
If local repositories are used, check that you updated these repositories with SAS Mirror Manager, as described above.
Check that your SAS repositories are enabled using yum:
If the status of "enabled" is not shown for the sas-* repositories, the repositories can be enabled by using yum-config-manager or by manually editing /etc/yum.repos.d/ files with enabled=1.
Check that your repository locations are accessible from all SAS Viya machines. For local repositories, list the directory paths or use curl to access the HTTP URLs specified in the baseurl values in /etc/yum.repos.d/sas.repos. For SAS hosted repositories, access can be checked via the steps in the deployment guide. See Internet Connectivity Problems. Every machine in the deployment needs access to the repositories.
Check /etc/yum.conf for any exclude statements that target SAS packages or repositories.
Refer to SAS Viya Hot Fix Availability.
Refer to SAS KB0036526, "Verify the installation of SAS® Viya® hot fixes in your Linux environment."