Pulp

Since the installer works on CentOS I imagine it already works on RHEL. If the installer doesn't work for some reason that would be good to fix.

Since I believe it works I read this not as a Story but as a Test activity. Also how will we assure this stays working over time?

This isn't just a test activity. New OS vars files will be created in the ansible-pulp repo for RHEL that will be necessary even if installing by hand.

This rewrite looks good to me. Thanks!

I attempted to use the installer to install Pulp 3 on RHEL7.6 subscribed box.

TASK [pulp : Load OS specific variables] *****************************************************************************
fatal: [192.168.122.7]: FAILED! => changed=false 
  ansible_facts: {}
  ansible_included_var_files: []
  message: |-
    Could not find or access 'RedHat.yml'
    Searched in:
            /tmp/tmp.1eoSX7RspC/ansible-pulp/roles/pulp/vars/RedHat.yml
            /tmp/tmp.1eoSX7RspC/ansible-pulp/roles/pulp/RedHat.yml
            /tmp/tmp.1eoSX7RspC/ansible-pulp/roles/pulp-database/vars/RedHat.yml
            /tmp/tmp.1eoSX7RspC/ansible-pulp/roles/pulp-database/RedHat.yml
            /tmp/tmp.1eoSX7RspC/ansible-pulp/roles/pulp/tasks/vars/RedHat.yml
            /tmp/tmp.1eoSX7RspC/ansible-pulp/roles/pulp/tasks/RedHat.yml
            /tmp/tmp.1eoSX7RspC/vars/RedHat.yml
            /tmp/tmp.1eoSX7RspC/RedHat.yml on the Ansible Controller.
    If you are using a module and expect the file to exist on the remote, see the remote_src option

PLAY RECAP ***********************************************************************************************************
192.168.122.7              : ok=5    changed=0    unreachable=0    failed=1   

Same playbook was used to install Pulp 3 on a CentOS7 box.

Some tips:

1. Until we have a need for them to differ, RedHat.yml should be a symlink to CentOS.yml .
2. You'll have to use different logic to add epel, because epel-release is not in RHEL.

For the RPM plugin, we will need createrepo_c 0.13.0+ , the most important functionality which we need there is a modular errata support. The motivation for this issue is to allow testing of the migration tool. We don't want to block testing of the tool for content types that are ready, so we can create a separate issue to handle RPM if necessary.

rchan wrote:

For the RPM plugin, we will need createrepo_c 0.13.0+ , the most important functionality which we need there is a modular errata support. The motivation for this issue is to allow testing of the migration tool. We don't want to block testing of the tool for content types that are ready, so we can create a separate issue to handle RPM if necessary.

1. As we discussed on IRC, for RHEL7 they do not build the python3-createrepo_c subpackage of "createrepo_c". This is a packaging change for the overall "createrepo_c" source RPM.

2. RHEL8 & 8.1 beta have python3-createrepo_c, but only at 0.11.0-1 . So we need the the overall createrepo_c package upgraded on RHEL8 as well.

I realized that the only RHEL repo we need to enable now is actually optional, not extras, since we are not trying to get libmodulemd from RHEL.

There are several common names for that repo, and many possible ones if managed by Katello/Satellite or other custom repo management.

I am working on enabling a list of several common names; the 1st one found only. It is more complex than you'd expect (yum-config-manager is easy to make idempotent.) It also lets users specify a list, or a specific name, instead.
https://github.com/pulp/ansible-pulp/pull/172

Other remaining work:

• Symlink/check CentOS vars yml files as RedHat ones.
• Similar list logic for "epel-release" vs the epel URL (the URL is equivalent to a package name)