You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2023. It is now read-only.
Hi,
Stuck on the worker node provisioning, would be good to get some help with this, these are the last few lines after from running the script "deploy_ne.sh "
using : OpenNESS 20.12.02 Release
--
Retrying task - attempt 9 of 10
Error occurred. Will retry after 5 seconds. You can find details below:
No package matching 'tuned-2.11.0-8.el7' found available, installed or updated
Retrying task - attempt 10 of 10
fatal: [node01]: FAILED! => {
"attempts": 10,
"changed": false,
"rc": 126,
"results": [
"No package matching 'tuned-2.11.0-8.el7' found available, installed or updated"
]
}
MSG:
No package matching 'tuned-2.11.0-8.el7' found available, installed or updated
NO MORE HOSTS LEFT *************************************************************************************************************************************************************
PLAY RECAP *********************************************************************************************************************************************************************
node01 : ok=85 changed=22 unreachable=0 failed=1 skipped=84 rescued=0 ignored=2
Regards,
ravi
The text was updated successfully, but these errors were encountered:
Hi. This happened to me once, and although I got around it by just commenting out the tuned-2.11.0-8.el7 line and setting tuned_skip to true in group_vars/edgenode_group/10-default.yml, eventually I reinstalled OpenNESS and didn't run into that error. The difference I can think of is that the first time I was using CentOS 7.6-1810 (I think this was the supported OS for OpenNESS 20.09) and now I switched CentOS 7.8-2003 (supported OS for OpenNESS 20.12).
Ok thanks Jorge, the OS matches..will keep that in mind for the worker node, but still stuck with the controller issue. Would you have insight on that ?, issue is with certificates for Harbor...
Hi,
Looks like the K8S controller installation went fine, but how do i validate that the controller services are up ?, dont see Kubectl configured either on the controller too to excute any related commands..any help ?, any openness references to validate the controller and worker node setup, before deploying some applications ?
thanks
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Stuck on the worker node provisioning, would be good to get some help with this, these are the last few lines after from running the script "deploy_ne.sh "
using : OpenNESS 20.12.02 Release
--
The text was updated successfully, but these errors were encountered: