-
Notifications
You must be signed in to change notification settings - Fork 166
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
/ansible scripts fail on Centos 6 #801
Comments
Oh, you know, I did this recently and ran into a ton of trouble because they've changed a bunch of stuff over at scientificlinux where we pull this from. Unfortunately I missed the memo that we'd finally made the switch to the new ansible stuff and did it in the old ansible tooling, I'd be grateful if you were able to do the conversion for me, otherwise just use the old playbook: #740 |
Is the old playbook non-functional without #740? How would you suggest to proceed with the compiler upgrade? Base it on your PR? I don't feel qualified to do the conversion due to insufficient knowledge about the build infrastructure. |
#740 is good to go, you could just use that to provision a centos6 machine, it's just not merged because ideally it should be against the new ansible infra instead. |
Is it planned to be merged soon? Otherwise my PR will be blocked. Or do you mean that #740 is waiting for the conversion? |
@seishun I just merged it, better than nothing at this stage so if you want to PR against CeotOS6 setup then you'd better do it against the old Ansible playbook unless you're going to do the conversion but there's no requirement that you do. |
pretty sure this is fixed and has moved on to discussions about which devtoolset, #1203 for one |
When running
ansible/ansible-playbook playbooks/jenkins/worker/create.yml
on a Centos 6 host, I get the following error:If I install libselinux-python manually, then the following happens:
Judging by the comments in the file, it seems
ansible/roles/baselayout/tasks/partials/repo/centos6.yml
is unfinished.The text was updated successfully, but these errors were encountered: