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.

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

Closed
seishun opened this issue Jul 18, 2017 · 6 comments
Closed

/ansible scripts fail on Centos 6 #801

seishun opened this issue Jul 18, 2017 · 6 comments

Comments

@seishun
Copy link
Contributor

seishun commented Jul 18, 2017

When running ansible/ansible-playbook playbooks/jenkins/worker/create.yml on a Centos 6 host, I get the following error:

TASK [baselayout : disable sftp] *******************************************************************************************************
fatal: [test-softlayer-centos6-x64-1]: FAILED! => {"changed": false, "failed": true, "msg": "Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!"}

If I install libselinux-python manually, then the following happens:

TASK [baselayout : repo : add scl devtoolset] ******************************************************************************************
fatal: [test-softlayer-centos6-x64-1]: FAILED! => {"changed": false, "failed": true, "msg": "missing required arguments: name"}

Judging by the comments in the file, it seems ansible/roles/baselayout/tasks/partials/repo/centos6.yml is unfinished.

@rvagg
Copy link
Member

rvagg commented Jul 21, 2017

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

@seishun
Copy link
Contributor Author

seishun commented Jul 21, 2017

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.

@rvagg
Copy link
Member

rvagg commented Jul 21, 2017

#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.

@seishun
Copy link
Contributor Author

seishun commented Jul 21, 2017

Is it planned to be merged soon? Otherwise my PR will be blocked.

Or do you mean that #740 is waiting for the conversion?

@rvagg
Copy link
Member

rvagg commented Jul 22, 2017

@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.

@rvagg
Copy link
Member

rvagg commented Apr 2, 2018

pretty sure this is fixed and has moved on to discussions about which devtoolset, #1203 for one

@rvagg rvagg closed this as completed Apr 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants