Skip to content
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.

Sign up for GitHub

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

Jump to bottom

viya_pre_install_playbook.yml fails on clientaliveinterval control even when you run the playbook with the exclude opti #69

Closed
JMPoilane opened this issue Oct 9, 2020 · 9 comments
Closed

viya_pre_install_playbook.yml fails on clientaliveinterval control even when you run the playbook with the exclude opti #69

JMPoilane opened this issue Oct 9, 2020 · 9 comments
Assignees
@kevinlinglesas
Labels
bug Something isn't working

Comments

@JMPoilane
Copy link

JMPoilane commented Oct 9, 2020 •
edited
Loading

Deployment of Viya 3.5 on Linux CentOS 7.
ansible-playbook 2.7.12
python version = 2.7.5

Attachment #1 is the playbook's verbose log without the option and fails as expected :
Your current SSH clientaliveinterval value (420) is smaller than the recommended value of 3600... Either update the value of clientaliveinterval in your SSHD config file, or, if you prefer to suppress this warning, re-run the playbook with a lower threshold by adding -e 'min_ssh_client_alive_internal=1' to the playbook execution command line."

Attachment #2 is the playbook's verbose log with the option and fails with same error as unexpected. So -e 'min_ssh_client_alive_internal=1' does not work

Is it normal ? If not cant it be fixed ?

My best regards.
nohup.out.erreur-1.zip
nohup.out.erreur-2.zip
@kevinlinglesas
Copy link
Collaborator

Thank you @JMPoilane for the issue. We will look closely at it and get back to you. Can you tell me what version of Ansible you were running?

@JMPoilane
Copy link
Author

JMPoilane commented Oct 9, 2020 via email

@JMPoilane
Copy link
Author

Hello,

Any update on this issue ?

Regards.

Jean-Marie

@kevinlinglesas
Copy link
Collaborator

Sorry @JMPoilane, not yet.

@erharb
Copy link
Member

erharb commented Oct 19, 2020 •
edited
Loading

@JMPoilane: To workaround for now you can modify the value in the main.yml which is used for the rule.

viya-ark/playbooks/pre-install-playbook/roles/viya-ark.preinstall/defaults/main.yml

Line 67 in 8cd03a3

min_clientaliveinterval_val: 3600

@JMPoilane
Copy link
Author

JMPoilane commented Oct 20, 2020 via email

@JMPoilane
Copy link
Author

Hello again,

a) I could make it work. You simply need to specify in playbook this correct argument :
-e 'min_clientaliveinterval_val=1'

b) Therefore it means that error message received with proposed workaround is wrong see :
... re-run the playbook with a lower threshold by adding -e 'min_ssh_client_alive_internal=1'

c) So instead of changing the value in main.yml it could be more logical to change the error message. Do you agree ? That would be :
... re-run the playbook with a lower threshold by adding -e 'min_clientaliveinterval_val=1'

@kevinlinglesas
Copy link
Collaborator

Hi Steve,

Yes, the error message needs to be changed. Thank you for helping us to identify this oversight. We will make the change in a future release.

@kevinlinglesas kevinlinglesas added the bug Something isn't working label Oct 20, 2020
@kevinlinglesas kevinlinglesas self-assigned this Jan 8, 2021
@kevinlinglesas
Copy link
Collaborator

Fixed by Viya35-ark-1.12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kevinlinglesas kevinlinglesas

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kevinlinglesas @erharb @JMPoilane