GalaxyKickStart for Centos

[Sinan81]

Hi,

I am wondering if there is a Centos version of GalaxyKickstart files. Would it be sufficient to replace vagrant box to a Centos one and replace 'apt ..' in galaxy.yml with 'yum ...'

[drosofff]

Hi,

There is currently no Centos version of GKS. I don't think it would be as easy as replacing ansible apt modules by ansible yum. On the other hand, it does not look as a very hard task. Since we will have to migrate GKS to release_18.01 or 18.04 in priority, you are welcome to test in the meantime. An approach would be to run the playbook on Centos and to fix step by step using the ansible installation log.

Best

[Sinan81]

Thanks.

Started with installing a compatible ansible version in a virtualenv and replacing 'apt' with 'yum. Afterwards, the first error I get is:

TASK [ensure_postgresql_up : service] ******************************************
task path: /home/sinan81/.vagrant_files/GalaxyKickStart/roles/ensure_postgresql_up/tasks/main.yml:2
Running systemd
Using module file /home/sinan81/.venv_ansible/lib/python2.7/site-packages/ansible/modules/core/system/systemd.py
<127.0.0.1> ESTABLISH SSH CONNECTION FOR USER: vagrant
<127.0.0.1> SSH: EXEC ssh -vvv -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=2222 -o 'IdentityFile="/home/sinan81/.vagrant_files/GalaxyKickStart/.vagrant/machines/default/virtualbox/private_key"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=30 -o ControlPath=/home/sinan81/.ansible/cp/ansible-ssh-%h-%p-%r 127.0.0.1 '/bin/sh -c '"'"'( umask 77 && mkdir -p "` echo $HOME/.ansible/tmp/ansible-tmp-1526001883.82-60331004840642 `" && echo ansible-tmp-1526001883.82-60331004840642="` echo $HOME/.ansible/tmp/ansible-tmp-1526001883.82-60331004840642 `" ) && sleep 0'"'"''
<127.0.0.1> PUT /var/tmp/tmp3YW6yQ TO /home/vagrant/.ansible/tmp/ansible-tmp-1526001883.82-60331004840642/systemd.py
<127.0.0.1> SSH: EXEC sftp -b - -vvv -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=2222 -o 'IdentityFile="/home/sinan81/.vagrant_files/GalaxyKickStart/.vagrant/machines/default/virtualbox/private_key"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=30 -o ControlPath=/home/sinan81/.ansible/cp/ansible-ssh-%h-%p-%r '[127.0.0.1]'
<127.0.0.1> ESTABLISH SSH CONNECTION FOR USER: vagrant
<127.0.0.1> SSH: EXEC ssh -vvv -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=2222 -o 'IdentityFile="/home/sinan81/.vagrant_files/GalaxyKickStart/.vagrant/machines/default/virtualbox/private_key"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=30 -o ControlPath=/home/sinan81/.ansible/cp/ansible-ssh-%h-%p-%r 127.0.0.1 '/bin/sh -c '"'"'chmod u+x /home/vagrant/.ansible/tmp/ansible-tmp-1526001883.82-60331004840642/ /home/vagrant/.ansible/tmp/ansible-tmp-1526001883.82-60331004840642/systemd.py && sleep 0'"'"''
<127.0.0.1> ESTABLISH SSH CONNECTION FOR USER: vagrant
<127.0.0.1> SSH: EXEC ssh -vvv -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=2222 -o 'IdentityFile="/home/sinan81/.vagrant_files/GalaxyKickStart/.vagrant/machines/default/virtualbox/private_key"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=30 -o ControlPath=/home/sinan81/.ansible/cp/ansible-ssh-%h-%p-%r -tt 127.0.0.1 '/bin/sh -c '"'"'sudo -H -S -n -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-ypnexaexvrubplrugwfewvwicsedzzym; /usr/bin/python /home/vagrant/.ansible/tmp/ansible-tmp-1526001883.82-60331004840642/systemd.py; rm -rf "/home/vagrant/.ansible/tmp/ansible-tmp-1526001883.82-60331004840642/" > /dev/null 2>&1'"'"'"'"'"'"'"'"' && sleep 0'"'"''
fatal: [default]: FAILED! => {
    "changed": false,
    "failed": true,
    "invocation": {
        "module_args": {
            "daemon_reload": false,
            "enabled": null,
            "masked": null,
            "name": "supervisor",
            "state": "started",
            "user": false
        }
    },
    "msg": "Could not find the requested service \"'supervisor'\": "
}
    to retry, use: --limit @/home/sinan81/.vagrant_files/GalaxyKickStart/galaxy.retry

PLAY RECAP *********************************************************************
default                    : ok=9    changed=1    unreachable=0    failed=1

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

It seems this is a known problem: https://github.com/ansible/ansible-modules-core/issues/915

[drosofff]

@Sinan81 In https://github.com/ansible/ansible-modules-core/issues/915, there is mention of bug still alive with ansible 2.2. Did you try to upgrade ansible, maybe it would make it.

[Sinan81]

I can upgrade ansible but the reason why I was using 2.2 is because that is the highest compatible ansible version mentioned in the GalaxyKickStart github welcome page.

[Sinan81]

I upgraded ansible to 2.5.2 and still getting the same error.

[zph001]

Would be very kind of you if GalaxyKickStart can be adopted on RHEL/CentOS

[drosofff]

Sure, unfortunately there is so many things to do... Have you considered running a GKS docker instance on your Centos ? do you think it would be an acceptable turnaround ?