Enforce/Document ansible >= 2.3

[akofink]

It seems ansible v. 2.2 has some issues with requiring module support code:

fatal: [localhost]: FAILED! => {"failed": true, "msg": "Could not find imported module support code for katello_upload.  Looked for either handle_no_nailgun or foreman_helper"}

[mdellweg]

OK for >= 2.3. Is it like Require: ansible >= 2.3.0 in the Documentation variable? Should we implement a test for this before failing to import handle_no_nailgun?

[akofink]

I believe so, like this.

[Fobhep]

@akofink I am currently trying to tackle that issue and I came up with a bunch of questions:

• can you confirm this being solved with v.2.3+ ?
• I did a bit of research and there are several modules in ansible that use import from module_utils before version 2.3. so I don't think v 2.2 is a general problem
• Did you try this with an ansible installation via package or via pip?
• Virtualenv or "native"?

[Fobhep]

Generally it seems a good idea to go not beyond a certain ansible version. I am just wondering wether we want to connect a failure to an ansible version being below a minimum, or to a failed import of module_utils or to both

[mdellweg]

From 2.3 Release notes:

Allow module_utils for custom modules to be placed in site-specific directories and shipped in roles

[Fobhep]

ok fair enough. I guess the older modules probabally use a shared module_utils for the whole ansible project

[akofink]

@Fobhep I believe I was using Python 2.7 native on Centos 7.4. It's been a couple months :thinking:. We've seen differences with virtualenv vs. native during debugging (i.e. using the hacking/test-module with -D).

[evgeni]

We documented this, and 2.3 is quite old. Shall this issue be closed? I'd say so :)