-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Viya 3.5 Pre-Install failed while running pre_install_playbook.yml #65
Comments
The Gathering facts phase is an ansible-playbook built-in, not something provided by Viya ARK. Most likely this is some kind of environment/installation problem with ansible itself. One thing I noticed is that while your default python is version 3.6.9, the version of python which ansible was installed with was Python 2.7: You might want to try either making python 2.7 the default python, or uninstalling ansible then install it using python 3's pip. |
Still looks to me an issue; Can you guide me some cleanup process, since If I remove ansible still Python out there. [sas@nhisasviyavm pre-install-playbook]$ ansible --version PLAY [localhost] *********************************************************************************************************************** TASK [Gathering Facts] ***************************************************************************************************************** |
ansible is still installed using python 2.7, did you attempt to uninstall it? What version does pip -V report? To make sure python 3 is used reinstall with "python -m pip install ansible" since python -V reports version 3. Beyond that you may want to file an issue with the Ansible project on Github here since your issue is not Viya ARK related: |
[sas@nhisasviyavm pre-install-playbook]$ pip -V report [sas@nhisasviyavm pre-install-playbook]$ sudo python -m pip install ansible |
My recollection is that you need to uninstall ansible using pip and re-install ansible using pip3 in order for python3 to be used inherently by ansible as I think you are trying to achieve. sudo pip uninstall --yes ansible |
Yes so use pip from version 2 to uninstall ansible, then use python 3's pip to install it. Since your default python is 3 you should probably update your path to make pip 3 default instead of pip 2 |
I am trying to do with python 2.7 only. I do not have python 3 now. So I have uninstalled ansible and re-install with pip only. Here is the different error now; [sas@nhisasviyavm ~]$ whereis python [sas@nhisasviyavm pre-install-playbook]$ ansible-playbook viya_pre_install_playbook.yml -i pre-install.inventory.ini Traceback (most recent call last): |
You might need to do a deeper clean after uninstall of ansible again, by removing the ansible folder under site-packages /usr/lib64/python2.7/site-packages, then installing again, similar to what was found here (though they had python 3, probably same problem of somehow bad download): |
After delete ansible folder issue got resolved finally :) thanks for the tip. However, I stuck here; TASK [viya-ark.preinstall : Check that required RHEL package 'nss.x86_64' is available in a repository at some version] **************** TASK [viya-ark.preinstall : Assert that package 'nss.x86_64' is available] ************************************************************* PLAY RECAP ***************************************************************************************************************************** sudo yum install nss-mdns.x86_64 |
What version of RHEL is this (on your deployTarget)? And do you have the RHEL repos properly entitled on your target? What happens if you try to manually run |
[sas@nhisasviyavm pre-install-playbook]$ cat /etc/redhat-release [sas@nhisasviyavm pre-install-playbook]$ sudo yum install nss.x86_64 |
Is deployTarget same host as the local host running ansible? |
yes. it is a single machine |
looks to me it is looking for latest version (3.36) though it had installed (3.28) it. I tried with upgrade but no luck. Any alternate solution ? TASK [viya-ark.preinstall : Check for installed RHEL package 'nss.x86_64'] ************************************************************* TASK [viya-ark.preinstall : Check that installed RHEL package 'nss.x86_64' meets minimum version 3.36.0-7] ***************************** TASK [viya-ark.preinstall : Set valid installed package flag] ************************************************************************** TASK [viya-ark.preinstall : Check that required RHEL package 'nss.x86_64' is available in a repository at some version] **************** |
I'm thinking maybe some RHEL repo isn't enabled that should be to pick up newer version of it. Are you using a mirror or direct to rhel's hosting? What does the output of yum repolist provide, and yum repoinfo for each RHEL repo provide? |
I am using Rhel hosting. Any instructions how to enable repos if something I missed?
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Eric Harbeston <notifications@github.com>
Sent: Monday, August 3, 2020 10:04:12 PM
To: sassoftware/viya-ark <viya-ark@noreply.github.com>
Cc: Toluchuri, Venkateswarlu <venkat.toluchuri@optum.com>; Author <author@noreply.github.com>
Subject: Re: [sassoftware/viya-ark] Viya 3.5 Pre-Install failed while running pre_install_playbook.yml (#65)
I'm thinking maybe some RHEL repo isn't enabled that should be to pick up newer version of it. Are you using a mirror or direct to rhel's hosting? What does the output of yum repolist provide, and yum repoinfo for each RHEL repo provide?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#65 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AET4YOM4IBUE2BZBP7S4OGTR63RIJANCNFSM4PTHCFCA>.
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
|
It appears the baseline required version of nss.x86_64 was made for Viya 3.5 to discontinue use of insecure TLS ciphers for various CVEs (nss >= 3.36.0-7, along with curl >= 7.19.7-53). Newer versions are available from the official Red Hat repos some time after RHEL 7.4. You will need to work with Red Hat tech support on how to get the required versions of nss and curl for these security reasons, or upgrade to a newer version of RHEL 7.x which has the required versions. |
I think RHEL 7.6 may be earliest version that comes with the correct version, also note that both 7.4 and 7.5 are already past their Red Hat extended update support lifecycle: https://access.redhat.com/support/policy/updates/errata/
|
If we do not have Install the version of (nss >= 3.36.0-7, along with curl >= 7.19.7-53) were there any issues with the Viya install ? So you recommend to have VM to be Redhat 7.7 instead 7.4 ? |
Yes those versions of nss and curl are required for Viya 3.5 to install and run successfully due to SAS requirements for security. RHEL 7.6 or higher so 7.7 should be fine. |
This is a Azure linux VM. Can I upgrade 7.4 to 7.6 just doing these commands instead relaunch another VM and redo all work?
echo 7.6 > /etc/yum/vars/releasever
sudo yum update
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Eric Harbeston <notifications@github.com>
Sent: Monday, August 3, 2020 10:48:14 PM
To: sassoftware/viya-ark <viya-ark@noreply.github.com>
Cc: Toluchuri, Venkateswarlu <venkat.toluchuri@optum.com>; Author <author@noreply.github.com>
Subject: Re: [sassoftware/viya-ark] Viya 3.5 Pre-Install failed while running pre_install_playbook.yml (#65)
Yes those versions of nss and curl are required for Viya 3.5 to install and run successfully due to SAS requirements for security. RHEL 7.6 or higher so 7.7 should be fine.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#65 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AET4YOJBR4LNQ7H7ZOLW4F3R63WNNANCNFSM4PTHCFCA>.
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
|
I don't know, you'd need to ask Azure tech support in that case. Usually sudo yum upgrade but not sure |
I am trying to run "ansible-playbook viya_pre_install_playbook.yml -i pre-install.inventory.ini -v --check" and failed with below ERROR. I had switched different Ansible version from 2.7 version to 2.9 however still no luck. But I am suspecting Issue should be python module could not load.
ansible --version
/usr/lib64/python2.7/site-packages/cryptography/init.py:39: CryptographyDeprecationWarning: Python 2 is no longer supported by the P
ython core team. Support for it is now deprecated in cryptography, and will be removed in a future release.
CryptographyDeprecationWarning,
ansible 2.7.2
config file = None
configured module search path = [u'/home/sas/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.5 (default, May 3 2017, 07:55:04) [GCC 4.8.5 20150623 (Red Hat 4.8.5-14)]
[sas@nhisasviyavm pre-install-playbook]$ python -V
Python 3.6.9
Please point me with the right fix here ?
ansible-playbook viya_pre_install_playbook.yml -i pre-install.inventory.ini -v --check
/usr/lib64/python2.7/site-packages/cryptography/init.py:39: CryptographyDeprecationWarning: Python 2 is no longer supported by the P
ython core team. Support for it is now deprecated in cryptography, and will be removed in a future release.
CryptographyDeprecationWarning,
No config file found; using defaults
/opt/sas/viya-ark/playbooks/pre-install-playbook/pre-install.inventory.ini did not meet host_list requirements, check plugin documentati
on if this is unexpected
/opt/sas/viya-ark/playbooks/pre-install-playbook/pre-install.inventory.ini did not meet script requirements, check plugin documentation
if this is unexpected
/opt/sas/viya-ark/playbooks/pre-install-playbook/pre-install.inventory.ini did not meet yaml requirements, check plugin documentation if
this is unexpected
PLAY [localhost] ***********************************************************************************************************************
TASK [Gathering Facts] *****************************************************************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ValueError: Attempted relative import i
n non-package
fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n File "/home/sas/.ansible/tmp/
ansible-tmp-1596452137.03-64750991737495/AnsiballZ_setup.py", line 113, in \n _ansiballz_main()\n File "/home/sas/.ansible
/tmp/ansible-tmp-1596452137.03-64750991737495/AnsiballZ_setup.py", line 105, in ansiballz_main\n invoke_module(zipped_mod, temp_pat
h, ANSIBALLZ_PARAMS)\n File "/home/sas/.ansible/tmp/ansible-tmp-1596452137.03-64750991737495/AnsiballZ_setup.py", line 48, in invoke
module\n imp.load_module('main', mod, module, MOD_DESC)\n File "/tmp/ansible_setup_payload_QfbLMQ/main.py", line 131, in <
module>\nValueError: Attempted relative import in non-package\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the
exact error", "rc": 1}
to retry, use: --limit @/opt/sas/viya-ark/playbooks/pre-install-playbook/viya_pre_install_playbook.retry
PLAY RECAP *****************************************************************************************************************************
localhost : ok=0 changed=0 unreachable=0 failed=1
The text was updated successfully, but these errors were encountered: