BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
Lapis Lazuli | Level 10



I have a mirror repository at /sas/install/sas_repos.

After setting up everything I run the system assessment playbook:


ansible-playbook system-assessment.yml

I get the following error:



TASK [Install sas-cleanutils] ***************************************************************************************************************************************************
fatal: [cas]: FAILED! => {"changed": false, "msg": "file:///sas/install/sas_repos/repos/shipped/depentviya/135/depentviya-135-x64_redhat_linux_6-yum/repodata/repomd.xml: [Errno 14] curl#37 - \"Couldn't open file /sas/install/sas_repos/repos/shipped/depentviya/135/depentviya-135-x64_redhat_linux_6-yum/repodata/repomd.xml\"\nTrying other mirror.\n\n\n One of the configured repositories failed (depentviya-135-x64_redhat_linux_6-yum),\n and yum doesn't have enough cached data to continue. At this point the only\n safe thing yum can do is fail. There are a few ways to work \"fix\" this:\n\n 1. Contact the upstream for the repository and get them to fix the problem.\n\n 2. Reconfigure the baseurl/etc. for the repository, to point to a working\n upstream. This is most often useful if you are using a newer\n distribution release than is supported by the repository (and the\n packages for the previous distribution release still work).\n\n 3. Run the command with the repository temporarily disabled\n yum --disablerepo=sas-depentviya-135-x64_redhat_linux_6-yum ...\n\n 4. Disable the repository permanently, so yum won't use it by default. Yum\n will then just ignore the repository until you permanently enable it\n again or use --enablerepo for temporary usage:\n\n yum-config-manager --disable sas-depentviya-135-x64_redhat_linux_6-yum\n or\n subscription-manager repos --disable=sas-depentviya-135-x64_redhat_linux_6-yum\n\n 5. Configure the failing repository to be skipped, if it is unavailable.\n Note that yum will try to contact the repo. when it runs most commands,\n so will have to try and fail each time (and thus. yum will be be much\n slower). If it is a very temporary problem though, this is often a nice\n compromise:\n\n yum-config-manager --save --setopt=sas-depentviya-135-x64_redhat_linux_6-yum.skip_if_unavailable=true\n\nfailure: repodata/repomd.xml from sas-depentviya-135-x64_redhat_linux_6-yum: [Errno 256] No more mirrors to try.\nfile:/sas/install/sas_repos/repos/shipped/depentviya/135/depentviya-135-x64_redhat_linux_6-yum/repodata/repomd.xml: [Errno 14] curl#37 - \"Couldn't open file /sas/install/sas_repos/repos/shipped/depentviya/135/depentviya-135-x64_redhat_linux_6-yum/repodata/repomd.xml\"\n", "rc": 1, "results": []}
ok: [deployTarget]

NO MORE HOSTS LEFT **************************************************************************************************************************************************************

PLAY RECAP **********************************************************************************************************************************************************************
cas : ok=64 changed=3 unreachable=0 failed=1
deployTarget : ok=54 changed=3 unreachable=0 failed=0
localhost : ok=13 changed=0 unreachable=0 failed=0




The repomd.xml file that it complains about exists:


[sasinst@l1162p0024 sas_viya_playbook]$ ls -l /sas/install/sas_repos/repos/shipped/depentviya/135/depentviya-135-x64_redhat_linux_6-yum/repodata/repomd.xml
-rw-r--r--. 1 sasinst sasinst 2149 Jan  2 20:56 /sas/install/sas_repos/repos/shipped/depentviya/135/depentviya-135-x64_redhat_linux_6-yum/repodata/repomd.xml
[sasinst@l1162p0024 sas_viya_playbook]$

Any ideas?




Accepted Solutions
Lapis Lazuli | Level 10

Turns out I forgot to make sas_repos available on the cas node.

Doing that solved the error.


View solution in original post

Lapis Lazuli | Level 10

Turns out I forgot to make sas_repos available on the cas node.

Doing that solved the error.


suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 1 in conversation