Audit claw-playbook for RHEL/CENTOS support PART I

[ajs6f]

We need to go through both our internal and external roles and audit them to see what already has support for RHEL/CENT systems.

The outcome of this ticket is a comprehensive list of what does and does not need work so that we can divide up the work into smaller tickets.

• apache
• composer
• drupal
• drupal-console
• drush
• geerlingguy.php

[ajs6f]

All of these roles appear to fail on Centos7 with the same error. This with

• Ansible 2.3.1.0, 2.3.2.0, or 2.4.0.0.
• Linux 3.10.0-693.5.2.el7.x86_64 Create Vagrant file... #1 SMP
• CentOS Linux release 7.4.1708 (Core)

[DigitLib]

Ansible installation via pip (2.4.1) will succesfully install geerlingguy.php

[whikloj]

@ajs6f if you want to try and trace that error I'd recommend PyCharm from JetBrains. They have a community version which is less full-featured but free.

[dannylamb]

Downloading the base box now to try it out for myself. I'm on vagrant 2.3.2.

[jonathangreen]

I think maybe the issue is this:
ansible-galaxy install -r requirements.yml composer -vvv
Are you meaning to install composer there?

https://github.com/Islandora-Devops/claw-playbook/blob/master/Vagrantfile#L45
I'd expect the ansible-galaxy command to look more like:
ansible-galaxy install --role-file=requirements.yml --roles-path=roles/external --force

Not sure if that is the issue or not, but it seems like it might be.

[ajs6f]

I'll try that @jonathangreen. Ansible newbies unite!

[ajs6f]

Holy smoke! @jonathangreen's tip seems to have made everything install successfully, or at least it claims to have. I will now be manually spot-checking the installs to see if they worked correctly for reals.

[whikloj]

@DigitLib what about 2.4.1, did it complete installing?

[ajs6f]

At this point I think everything did indeed work. To put that another way, in my simple spot testing, I didn't find anything that didn't work. Go @geerlingguy!

[dannylamb]

@ajs6f @DigitLib It seems like both of your lists will work. Shall we close both of your tickets and move on to our internal roles? Those will get unlocked after #749 gets resolved.

[ajs6f]

Works for me, @dannylamb . You mean doing the same thing, but for our internal roles, right?

[DigitLib]

@dannylamb Ok.

[dannylamb]

@ajs6f Yep. Once the bootstrapping is taken care of, the roles can be tested more or less individually if we want to make another list and split it up.

@DigitLib 👍

Let's close these two out.