Comment 2 for bug 1762130

Even in XS7.1, there is also a dependence issue:
[root@xrtuk-11-13 plugins]# python -m agent.py
/usr/bin/python: No module named future

agent.py is invoked only when the instance agent is enabled (by default it's disabled), so it's not detected in CI job.

In XS7.0

[root@xrtmia-02-03 plugins]# for f in $files; do python -m $f 2>&1; done | grep -v "\.py"
/usr/bin/python: No module named future
/usr/bin/python: No module named future
/usr/bin/python: No module named six.moves
/usr/bin/python: No module named six
/usr/bin/python: No module named six

[root@xrtmia-02-03 plugins]# egrep 'six|future' *
agent.py:from future import standard_library
Binary file agent.pyc matches
glance.py: from six.moves import http_client as httplib
glance.py:from six.moves import urllib
glance.py:from six.moves.urllib.parse import urlparse
Binary file glance.pyc matches
utils.py: the future. This can occur during a migration if the clocks on the two
Binary file utils.pyc matches
xenhost.py:import six
xenhost.py: import six.moves.xmlrpc_client as xmlrpclib
xenhost.py: if not isinstance(cmd, six.string_types):