geerlingguy/ansible-role-repo-remi

Ansible Role - Remi RPM Repository for RHEL/CentOS

Ansible Role: Remi Repository

Installs Remi's RPM repository for RHEL/CentOS.

Requirements

On RHEL 8 or newer, you should make sure to install or enable the EPEL repository. I recommend using the geerlingguy.repo-epel repository.

Role Variables

Available variables are listed below, along with default values (see defaults/main.yml):

remi_repo_url: "https://rpms.remirepo.net/enterprise/remi-release-{{ ansible_distribution_major_version }}.rpm"

The URL from which the Remi repo .rpm will be downloaded and installed.

remi_repo_gpg_key_url: "https://rpms.remirepo.net/enterprise/{{ ansible_distribution_major_version }}/RPM-GPG-KEY-remi"

Remi repo GPG key location. Can be set to a local file or to the URL from Remi's website.

Dependencies

None.

Example Playbook

- hosts: servers
  roles:
    - geerlingguy.repo-remi

License

MIT / BSD

Author Information

This role was created in 2014 by Jeff Geerling, author of Ansible for DevOps.

ansible-role-repo-remi's Issues

Confusion over python 2 vs 3

Hey Jeff,

I am trying to stabilize my containers and roles. I thought getting testing up to python3 across OS would do it, but it seems to fail remirepo:

From https://github.com/opendevshop/devshop/runs/674739569?check_suite_focus=true#step:4:480

TASK [geerlingguy.repo-remi : Install remi repo.] ******************************
fatal: [devshop.586.centos7.actions.github.com]: FAILED! => changed=false 
  msg: The Python 2 bindings for rpm are needed for this module. If you require Python 3 support use the `dnf` Ansible module instead.. The Python 2 yum module is needed for this module. If you require Python 3 support use the `dnf` Ansible module instead.

I don't really understand why. You seem to have working python2 and 3 branches in the centos7-ansible containers?

When I changed back to python2 for centos7, ansible still tried to use python2! https://github.com/opendevshop/devshop/runs/674796855?check_suite_focus=true#step:4:418

Help? I've spent WAY too much time messing with python defaults!

When I run this along with the geerlingguy.repo-epel role, I get error

The error I get is:

TASK [geerlingguy.repo-remi : Install remi repo.] ******************************
fatal: [pg-vagrant]: FAILED! => {"changed": true, "failed": true, "msg": "Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again\n", "rc": 1, "results": ["Loaded plugins: fastestmirror\nSetting up Install Process\nExamining /var/tmp/yum-root-Ji5X34/remi-release-6.rpm: remi-release-6.6-2.el6.remi.noarch\nMarking /var/tmp/yum-root-Ji5X34/remi-release-6.rpm to be installed\nLoading mirror speeds from cached hostfile\n"]}

add dependency on epel

According to remirepo.net the repo has the following requirements:

• Fedora : RPM Fusion
• RHEL : Optional and EPEL
• CentOS : EPEL

Should those not be listed in the readme as requirements? One could also add role dependencies in meta/main, but that would be requirements on specific roles. Maybe someone is not using your epel role yet. ;)

Getting GPG key validation failures in projects using this role

For example:

TASK [geerlingguy.repo-remi : Install remi repo.] ******************************
fatal: [instance]: FAILED! => {"changed": false, "msg": "Failed to validate GPG signature for remi-release-8.1-2.el8.remi.noarch"}

From failed geerlingguy.php role build: https://travis-ci.org/github/geerlingguy/ansible-role-php/jobs/724625896

I pinged Remi on Twitter, and he mentioned: https://twitter.com/RemiRepository/status/1302910610724847616

Install remi repo

Ubuntu 18.04
virtualbox 5.2.34
Vagrant 2.2.3
ansible 2.8.0
composer 1.9.1
I am running centos7 guest on ubuntu 18.04. I'm getting

TASK [geerlingguy.repo-remi : Install remi repo.] ******************************
fatal: [oppsvm]: FAILED! => {"changed": false, "msg": "Failure downloading http://rpms.remirepo.net/enterprise/remi-release-7.rpm, Request failed: <urlopen error [Errno -2] Name or service not known>"}
The same vagrant box works fine on mac os catalina.

Thanks
Milton

geerlingguy.repo-remi not working on rhel8

Hello sir :-)

geerlingguy.repo-remi is not working on rhel8

TASK [geerlingguy.repo-remi : Install remi repo.] ******************************
fatal: [rhel8]: FAILED! => changed=false
  failures: []
  msg: |-
    Depsolve Error occured:
     Problem: conflicting requests
      - nothing provides epel-release = 8 needed by remi-release-8.1-2.el8.remi.noarch
  rc: 1
  results: []

tested with:

  - name: rhel8
    image: "geerlingguy/docker-${MOLECULE_DISTRO:-ubi8}-ansible:latest"
    command: ${MOLECULE_DOCKER_COMMAND:-""}
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: true

Use CDN for GPG key URL (at least)

See: geerlingguy/ansible-role-php#337 (comment)

Basically, we want to make it so it's easy to keep the role functioning even if @remicollet's main server infrastructure has some issues, like it did in late July for a couple days. See that issue for the details.

No package php-xmlrpc available on rhel 9

Hi @geerlingguy i have error ansible running role.yaml
fatal: [node4]: FAILED! => {"changed": false, "failures": ["No package php-xmlrpc available."], "msg": "Failed to install some of the specified packages", "rc": 1, "results": []}
fatal: [node5]: FAILED! => {"changed": false, "failures": ["No package php-xmlrpc available."], "msg": "Failed to install some of the specified packages", "rc": 1, "results": []}
can you help me?

Certification-verify fails at fetching https://rpms.remirepo.net/RPM-GPG-KEY-remi2018 (CentOS 7)

With the latest CentOS 7 vagrant-box repo-remi fails:

TASK [geerlingguy.repo-remi : Import remi GPG key.] ****************************
fatal: [vagrant]: FAILED! => {"changed": false, "msg": "failed to fetch key at https://rpms.remirepo.net/RPM-GPG-KEY-remi2018 , error was: Request failed: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)>"}

Reproduceable with:
python -c 'import urllib; urllib.urlretrieve("https://rpms.remirepo.net/RPM-GPG-KEY-remi2018")'

Problem is that the ca-certificates are too old, if works after updating with:
yum update -y ca-certificates

Would be niece to have variable to pick PHP version

Remi supports multiple versions of PHP. Now only default one will be used.

Failure downloading http://rpms.remirepo.net/enterprise/remi-release-7.rpm

I'm getting this error (full text provided below) when trying to 'vagrant up' any/all drupal-vm instances I have today. I've tried this with different versions of VirtualBox and Vagrant on different hosts, and with both old and new clones of drupal-vm/master with the same result in all cases thus far.

The host I am currently working from has all new VB and Vagrant so I'm going to try a couple of things...like switching from CentOS to Ubuntu, and cloning drupal-vm/master without modification and trying to get something up and running.

FAILED! => {"changed": false, "failed": true, "msg": "Failure downloading http://rpms.remirepo.net/enterprise/remi-release-7.rpm, [Errno 104] Connection reset by peer"}

[Errno 104] Connection reset by peer

I'm getting this today...

TASK [geerlingguy.repo-remi : Install remi repo.] ******************************
fatal: [drupalvm]: FAILED! => {"changed": false, "failed": true, "msg": "Failure downloading http://rpms.remirepo.net/enterprise/remi-release-7.rpm, [Errno 104] Connection reset by peer"}

5.6 and other repositories?

@geerlingguy:
Can this role also add other remi-PHP-repositories, like Remi's PHP 5.6 RPM repository for Enterprise Linux 7 - x86_64 ?

Task ordering can cause gpg checking errors

In our deployment to RHEL8, we encountered some issues around the GPG Key validation. It seems to be solved by reversing the order of the tasks in main.yml. I will submit a pull request to have you review the issue @geerlingguy.

Fails on a Vagrant Centos 7.4

First time using the role but it is failing on a Centos 7.4 vagrant box. I think it is a key issue.

TASK [geerlingguy.repo-remi : Install remi repo.] ****************************** fatal: [ansible.dev]: FAILED! => {"changed": false, "msg": "warning: /tmp/remi-release-7Of2mls.rpm: Header V4 DSA/SHA1 Signature, key ID 00f97f56: NOKEY\n\n\nPublic key for remi-release-7Of2mls.rpm is not installed\n", "rc": 1, "results": ["Loaded plugins: fastestmirror\nExamining /tmp/remi-release-7Of2mls.rpm: remi-release-7.4-2.el7.remi.noarch\nMarking /tmp/remi-release-7Of2mls.rpm to be installed\nResolving Dependencies\n--> Running transaction check\n---> Package remi-release.noarch 0:7.4-2.el7.remi will be installed\n--> Finished Dependency Resolution\n\nDependencies Resolved\n\n================================================================================\n Package Arch Version Repository Size\n================================================================================\nInstalling:\n remi-release noarch 7.4-2.el7.remi /remi-release-7Of2mls 15 k\n\nTransaction Summary\n================================================================================\nInstall 1 Package\n\nTotal size: 15 k\nInstalled size: 15 k\nDownloading packages:\n"]}

From a brief search I couldn't tell if 7.4 was supported or not.

gpg: no valid OpenPGP data found. gpg: processing message failed: Unknown system error

I've been getting this error ever since I updated to Ansible 2.4

gpg: no valid OpenPGP data found. gpg: processing message failed: Unknown system error

This is on Centos7. I'm using a Vagrant image. Image version 1708.1

The error does not occur on Ansible 2.3.2

Use correct GPG-key per version

ansible-role-repo-remi uses a hardcoded GPG-key of Remi:

ansible-role-repo-remi/defaults/main.yml

Lines 1 to 3 in 765c0cc

	---
	remi_repo_url: "https://rpms.remirepo.net/enterprise/remi-release-{{ ansible_distribution_major_version }}.rpm"
	remi_repo_gpg_key_url: "https://rpms.remirepo.net/RPM-GPG-KEY-remi2018"

But they key is renewed every year. So it has to be manually overriden with the new option remi_repo_gpg_key_url as written at #27 (comment)

Remi now publishes the corresponding gpg-key at each repository (see remicollet/remirepo#234):
https://rpms.remirepo.net/enterprise/<version>/RPM-GPG-KEY-remi
So the same dynamic version-number like at remi_repo_url can be used.

remi_repo_url

It failed with http but worked with https in ../defaults/main.yml