As per my understandig, yum vs pip will not make any difference as long as you get the correct ansible version.    It seems Ansible had zypper module in earlier versions but it has been removed in some recent releases. SAS playbook uses zypper and is not found in recent Ansible versions. So, don't have any other workaround in mind as in my case just downgrading Ansible resolved the issue.  ... View more

Did you uninstall other version(s), if any? ... View more

Yes, that resolved the issue for me.   # rpm -qa | grep ansible ansible-core-2.12.2-4.el8_6.x86_64 # cat /etc/redhat-release Red Hat Enterprise Linux release 8.7 (Ootpa) ... View more

Correction - had to downgrade to 2.12.  ... View more

We had to downgrade Ansible to before 2.8.4 as per a suggestion from SAS support. ... View more

Thank you @gwootton . Sincerely appreciate your help. ... View more

Thank you @gwootton ... have gone through the deployment process 3 times, each time going through the pre-installation tasks to ensure not missing any pre-req items. Also, didn't notice any specific step for PostgreSQL installation and configuration. All 3 times it failed with only one error (or that's the only one I noticed) related to rabbitmq and that too the service comes up without any error on first restart after setting the admin password. So, not sure what should I do differently... any hint?    =======            "Tue Apr 26 19:01:58 EDT 2022 setup_rabbit_cluster Starting sas-viya-rabbitmq-server-default",         "Tue Apr 26 19:03:04 EDT 2022 setup_rabbit_cluster The RabbitMQ service sas-viya-rabbitmq-server-default could not be started.",         "Tue Apr 26 19:03:04 EDT 2022 setup_rabbit_cluster Returned status was 1",         "Tue Apr 26 19:03:04 EDT 2022 setup_rabbit_cluster Setup failed. Beware of independent Rabbit hosts running with different shared secrets."     ] }   NO MORE HOSTS LEFT ************************************************************************************************************************************************************   PLAY RECAP ******************************************************************************************************************************************************************** deployTarget               : ok=369  changed=136  unreachable=0    failed=1    skipped=853  rescued=0    ignored=0 localhost                  : ok=12   changed=2    unreachable=0    failed=0    skipped=6    rescued=0    ignored=0 ================== after changing admin password and restarting all services  sas_viya_playbook]# systemctl status sas-viya-rabbitmq-server-default ● sas-viya-rabbitmq-server-default.service - LSB: start and stop sas-rabbitmq-server server Loaded: loaded (/etc/rc.d/init.d/sas-viya-rabbitmq-server-default; generated) Active: active (running) since Sun 2022-05-01 22:46:13 EDT; 1 day 19h ago Docs: man:systemd-sysv-generator(8) Process: 91371 ExecStop=/etc/rc.d/init.d/sas-viya-rabbitmq-server-default stop (code=exited, status=0/SUCCESS) Process: 94438 ExecStart=/etc/rc.d/init.d/sas-viya-rabbitmq-server-default start (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 410046) Memory: 1.6M CGroup: /system.slice/sas-viya-rabbitmq-server-default.service └─16408 /bin/bash /opt/sas/viya/home/sbin/rabbitmq-server May 01 22:44:40 sildevdeapetan05.dol.gov su[94928]: pam_unix(su-l:session): session opened for user sasrabbitmq by (uid=0) May 01 22:45:22 sildevdeapetan05.dol.gov sas-viya-rabbitmq-server-default[94438]: sas-viya-rabbitmq-server-default service is registered May 01 22:45:36 sildevdeapetan05.dol.gov su[98503]: (to sasrabbitmq) root on none May 01 22:45:36 sildevdeapetan05.dol.gov su[98503]: pam_unix(su-l:session): session opened for user sasrabbitmq by (uid=0) May 01 22:45:37 sildevdeapetan05.dol.gov su[98575]: (to sasrabbitmq) root on none May 01 22:45:37 sildevdeapetan05.dol.gov su[98575]: pam_unix(su-l:session): session opened for user sasrabbitmq by (uid=0) May 01 22:45:59 sildevdeapetan05.dol.gov su[99775]: (to sasrabbitmq) root on none May 01 22:45:59 sildevdeapetan05.dol.gov su[99775]: pam_unix(su-l:session): session opened for user sasrabbitmq by (uid=0) May 01 22:46:13 sildevdeapetan05.dol.gov sas-viya-rabbitmq-server-default[94438]: sas-viya-rabbitmq-server-default service is started May 01 22:46:13 sildevdeapetan05.dol.gov systemd[1]: Started LSB: start and stop sas-rabbitmq-server server. [sas_viya_playbook]#     ======= all data related services are down sas-viya-dataplans-default down N/A N/A N/A sas-viya-report-data-default down N/A N/A N/A sas-viya-web-data-access-default down N/A N/A N/A sas-viya-dataexplorer-default down N/A N/A N/A sas-viya-dataprofiles-default down N/A N/A N/A sas-viya-datastudio-default down N/A N/A N/A sas-viya-dmdataservices-default down N/A N/A N/A   ================ ports open [sas_viya_playbook]# netstat -ntpl Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 10.50.12.103:50846 0.0.0.0:* LISTEN 28358/java tcp 0 0 10.50.12.103:10334 0.0.0.0:* LISTEN 28357/java tcp 0 0 0.0.0.0:40799 0.0.0.0:* LISTEN 28357/java tcp 0 0 0.0.0.0:43139 0.0.0.0:* LISTEN 15722/objspawn tcp 0 0 0.0.0.0:5671 0.0.0.0:* LISTEN 17075/beam.smp tcp 0 0 127.0.0.1:199 0.0.0.0:* LISTEN 1933/snmpd tcp 0 0 10.50.12.103:47816 0.0.0.0:* LISTEN 28358/java tcp 0 0 0.0.0.0:25672 0.0.0.0:* LISTEN 17075/beam.smp tcp 0 0 0.0.0.0:8200 0.0.0.0:* LISTEN 10921/vault tcp 0 0 0.0.0.0:8201 0.0.0.0:* LISTEN 10921/vault tcp 0 0 0.0.0.0:14443 0.0.0.0:* LISTEN 28358/java tcp 0 0 0.0.0.0:8300 0.0.0.0:* LISTEN 8542/consul tcp 0 0 0.0.0.0:8301 0.0.0.0:* LISTEN 8542/consul tcp 0 0 10.50.12.103:56431 0.0.0.0:* LISTEN 28357/java tcp 0 0 0.0.0.0:8591 0.0.0.0:* LISTEN 15722/objspawn tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/systemd tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 14117/httpd tcp 0 0 127.0.0.1:43473 0.0.0.0:* LISTEN 15722/objspawn tcp 0 0 0.0.0.0:4369 0.0.0.0:* LISTEN 15110/epmd tcp 0 0 10.50.12.103:59570 0.0.0.0:* LISTEN 28357/java tcp 0 0 0.0.0.0:37459 0.0.0.0:* LISTEN 28358/java tcp 0 0 0.0.0.0:8500 0.0.0.0:* LISTEN 8542/consul tcp 0 0 0.0.0.0:8501 0.0.0.0:* LISTEN 8542/consul tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1922/sshd tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1939/cupsd tcp 0 0 0.0.0.0:15672 0.0.0.0:* LISTEN 17075/beam.smp tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 4872/master tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 14117/httpd [sas_viya_playbook]# ... View more

@gwootton  Do I need to install PostgreSQL as a prereq before running the ansible playbook site.yml for deployment or the playbook will install and configure it? Thank you. ... View more

Thank you @gwootton . Seems that these requirements are for the data which we want to analyzed through SAS - not for the database required for SAS config itself (like bundled PostgreSQL). I was confused with that and can keep this config for later part as current requirement is satisfied by importing CSV files. However, need to resolve the postgre related error as replied in other post. Any hint on that will be much appreciated. Thanks. ... View more

@gwootton Thank you for solving the mystery. I was able to narrow down that zypper error is coming if I run the deployment as root and does not get the error if deployment is run as the account created for SAS processes/admin. Your answer clarified about the reason - the difference is Ansible versions - root is using v2.10.17 and SAS admin account is using 2.9.27 (as 2.10.17 available at the system level did not pass the assessment test). Thank you so much for your help.    ... View more

Thank you for replying @gwootton .   I don't see any of following directories/scripts as referenced in SAS Help Center: SAS Infrastructure Data Server. /opt/sas/viya/config/data/sasdatasvrc/ /etc/init.d/sas-viya-sasdatasvrc*   # ls -ltr /opt/sas/viya/config/data/ | grep data drwxr-x--- 2 sas sas 4096 Sep 10 2021 dmdataservices drwxr-x--- 2 sas sas 4096 Sep 10 2021 dataplans drwxr-x--- 2 sas sas 4096 Sep 10 2021 datastudio drwxr-x--- 2 sas sas 4096 Sep 15 2021 dataexplorer drwxr-x--- 2 sas sas 4096 Jan 6 16:15 web-data-access drwxr-x--- 2 sas sas 4096 Jan 21 10:08 report-data drwxr-x--- 2 sas sas 4096 Feb 1 15:10 dataprofiles   # ls -ltr /etc/init.d/ | grep data -rwxr-xr-x 1 sas sas 6617 Sep 10 2021 sas-viya-dmdataservices-default -rwxr-xr-x 1 sas sas 6546 Sep 10 2021 sas-viya-dataplans-default -rwxr-xr-x 1 sas sas 6564 Sep 10 2021 sas-viya-datastudio-default -rwxr-xr-x 1 sas sas 6582 Sep 15 2021 sas-viya-dataexplorer-default -rwxr-xr-x 1 sas sas 6594 Jan 6 16:15 sas-viya-web-data-access-default -rwxr-xr-x 1 sas sas 6561 Jan 21 10:08 sas-viya-report-data-default -rwxr-xr-x 1 sas sas 6573 Feb 1 15:10 sas-viya-dataprofiles-default   Seems that might be because the document is still referring to old version of PostgreSQL whereas I see service named sas-postgresql11   [root@sildevdeapetan05 avipani]# ls -ltr /etc/init.d/*post* -rwxr-xr-x 1 sas sas 6545 Dec 1 16:40 /etc/init.d/sas-postgresql11   [root@sildevdeapetan05 avipani]# /etc/init.d/sas-postgresql11 status ● sas-postgresql11.service - LSB: start and stop PostgreSQL server Loaded: loaded (/etc/rc.d/init.d/sas-postgresql11; generated) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) # ls -ltr /opt/sas/viya/config/var/log/sasdatasvrc ls: cannot access '/opt/sas/viya/config/var/log/sasdatasvrc': No such file or directory   [root@sildevdeapetan05 avipani]# /etc/init.d/sas-postgresql11 start Starting sas-postgresql11 (via systemctl): Job for sas-postgresql11.service failed because the service did not take the steps required by its unit configuration. See "systemctl status sas-postgresql11.service" and "journalctl -xe" for details. [FAILED] [root@sildevdeapetan05 avipani]# systemctl status sas-postgresql11.service ● sas-postgresql11.service - LSB: start and stop PostgreSQL server Loaded: loaded (/etc/rc.d/init.d/sas-postgresql11; generated) Active: failed (Result: protocol) since Mon 2022-05-09 11:59:48 EDT; 19s ago Docs: man:systemd-sysv-generator(8) Process: 2548652 ExecStart=/etc/rc.d/init.d/sas-postgresql11 start (code=exited, status=5) May 09 11:59:48 sildevdeapetan05.dol.gov systemd[1]: Starting LSB: start and stop PostgreSQL server... May 09 11:59:48 sildevdeapetan05.dol.gov systemd[1]: sas-postgresql11.service: Can't open PID file /var/run/postmaster.5432.> May 09 11:59:48 sildevdeapetan05.dol.gov systemd[1]: sas-postgresql11.service: Failed with result 'protocol'. May 09 11:59:48 sildevdeapetan05.dol.gov systemd[1]: Failed to start LSB: start and stop PostgreSQL server. lines 1-10/10 (END) ... View more

Thank you for replying. Sure, will work with tech support. ... View more

Sajid, Thank you for replying and clarifying that zypper is for SLES; however, I have mirrored repository only for Red Hat and installing on Red Hat as well.  # ./mirrormgr mirror --deployment-data SAS_Viya_deployment_data.zip  -p /mnt/gfs/temp/sas_repos/ --platform x64-redhat-linux-6 Mirroring 1/16 repos/shipped/depentviya/136/depentviya-136-x64_redhat_linux_6-yum Mirroring 2/16 repos/shipped/espcasvcf/135/espcasvcf-135-x64_redhat_linux_6-yum Mirroring 3/16 repos/shipped/odbc/125/odbc-125-x64_redhat_linux_6-yum Mirroring 4/16 repos/shipped/oracle/125/oracle-125-x64_redhat_linux_6-yum Mirroring 5/16 repos/shipped/pcfile/125/pcfile-125-x64_redhat_linux_6-yum Mirroring 6/16 repos/shipped/statviya/125/statviya-125-x64_redhat_linux_6-yum Mirroring 7/16 repos/shipped/va/125/va-125-x64_redhat_linux_6-yum Mirroring 8/16 repos/shipped/vcmnfnd/126/vcmnfnd-126-x64_redhat_linux_6-yum 45.24 GiB / 45.24 GiB [=========================================================] 100.00% 117.05 MiB/s 6m35s Mirroring 9/16 sasmd/shipped/depentviya/136/depentviya-136-x64_redhat_linux_6-yumsasmd 147.05 KiB / 147.05 KiB [===========================================================] 100.00% 57.87 KiB/s 2s Mirroring 10/16 sasmd/shipped/espcasvcf/135/espcasvcf-135-x64_redhat_linux_6-yumsasmd 253.67 KiB / 253.67 KiB [===========================================================] 100.00% 67.03 KiB/s 3s Mirroring 11/16 sasmd/shipped/odbc/125/odbc-125-x64_redhat_linux_6-yumsasmd 128.88 KiB / 128.88 KiB [===========================================================] 100.00% 53.63 KiB/s 2s Mirroring 12/16 sasmd/shipped/oracle/125/oracle-125-x64_redhat_linux_6-yumsasmd 137.40 KiB / 137.40 KiB [===========================================================] 100.00% 56.92 KiB/s 2s Mirroring 13/16 sasmd/shipped/pcfile/125/pcfile-125-x64_redhat_linux_6-yumsasmd 28.78 KiB / 28.78 KiB [=============================================================] 100.00% 38.88 KiB/s 0s Mirroring 14/16 sasmd/shipped/statviya/125/statviya-125-x64_redhat_linux_6-yumsasmd 2.40 MiB / 2.40 MiB [=============================================================] 100.00% 125.89 KiB/s 19s Mirroring 15/16 sasmd/shipped/va/125/va-125-x64_redhat_linux_6-yumsasmd 5.63 MiB / 5.63 MiB [=============================================================] 100.00% 161.56 KiB/s 35s Mirroring 16/16 sasmd/shipped/vcmnfnd/126/vcmnfnd-126-x64_redhat_linux_6-yumsasmd 3.37 MiB / 3.37 MiB [=============================================================] 100.00% 127.74 KiB/s 27s Done ... View more