does the rpm resolve all dependencies? in particular the colorama and prettytable ones?

Nope.

No, I haven't found how you can do that.

Also, do we want to pull that in with the general panc rpm? Might be worth splitting off panlint into a independent python package?

well, the very least requirements is that the panlint works. i'm not sure how critical the colorama and prettytable are for the functionality, but if not critical, wrap the imports in try/except and deal with the missing modules in the code.
to add dependencies, have a look at https://github.com/quattor/CCM/blob/master/pom.xml#L278
if the rpms are in epel or main repo, it's ok
if not, we need to add them to the externals repo

As @jrha mentioned that he's working on panlint, I will hold off any refactoring until I see a PR.

prettytable can easily be made optional, colorama is only used for colors which can also be made optional.

I've updated this to also include the dependencies of panlint in the pan rpm. It's currently hard set to python2. Maybe we should split it off in a independent rpm with a python2 and python3 flavour?

With Python2 reaching EOL on January 1st 2020, we should probably only be targeting Python3.

panlint calls #!/usr/bin/env python -- do we believe it currently works on py2 and py3? We could continue to make it work on py2 but only ship py3 support in the rpm?

At this moment it works both under python2 and python3 but I'm all in favour of focusing on python3.

@wpoely86 - cool, so what's blocking here? Remove the merge commit from this branch, rebase on master, make it work with py3 and we can merge?

@hpcugentbot please test this please

I've verified that the Maven tests all pass correctly locally, the RPM is built with the correct dependencies and installs correctly.
Seems like Jenkins is having issues again.