Pulp

This is waiting on https://pulp.plan.io/issues/5890 to be figured out in greater detail.

mdepaulo@redhat.com wrote:

This is waiting on https://pulp.plan.io/issues/5890 to be figured out in greater detail.

It is still being figured out, but is proceeding along, and we should proceed with the current design.

Per the CI team meeting on 2020-01-22, let's instead run against all pythons in CRON, but only against 3.6 (EL7/EL8 main version) on PRs.

This is because the entire pulp org shares the same number of jobs.

pulp_rpm_prerequisites needs this as well.

FYI, per my email to pulp-dev:

Hi CI & Installer teams,

I talked with James Tanner (who works on Ansible Core), and his advice was that we should not bother to test our ansible-pulp (a collection of roles) against multiple versions of Python on the management node (the Travis host.)

We still need to test a variety of Linux distros (with their bundled python versions) for managed nodes, which we do (molecule creates containers for multiple distros.)

This is because we meet the following criteria:

1. We do not write any python code, "action plugins" that run on the management node (and none for the managed node either, like role-bundled modules.)
2. We use few "action plugins" on the management node (the "package" module includes one to decide whether to use dnf/yum/apt/etc), and those we do use are probably all well tested by Ansible's first-party CI. It's difficult to enumerate those we use, and not worth enumerating. It's not like we use community-supported action plugins.

If there are no objections, I will create a low redmine tasks to make our Travis PR approach (static test case on Python 2.7 only, upgrade test case on 3.6 only, dynamic test case on 3.7 only) replace our complete 3x3 matrix approach of cron jobs.

If in the future we do not test every version of Python on the management node, we should not be overly concerned either.

-Mike

I am not suggesting we remove the 3x3 cron CI matrix we have right now, but remove them in the future if time requires us to.

As a follow up to #15: During the development of #6644, we ran into a Python 2.7 only bug when doing something like this: https://gist.github.com/kcem/5ec90b97c08fafd0397f248e8c31b25b#file-ansible_template_dict-yml-L12

When we recreated pulp_install_plugins with the dictionary keys (pulp_file) renamed (pulp-file), we got: {"u'source_dir'": u"u'/var/lib/pulp/devel/pulp_file'"} instead of: {u'source_dir': u'/var/lib/pulp/devel/pulp_file'}

So we should keep the Python 2.7 management node tests