As part of the move to zuul jobs building images we've discovered we
have a couple of scripts that are invoked by python2. Python2 isn't
available be default in the test images and python2 is old enough now
that we should just use python3. This change updates things to make it
so.
We also drop initialize-urandom from our arm builds. We haven't used
this with x86 in some time and it was only really an issue for xenial
anyway. If x86 xenial doesn't need it then arm shouldn't either.
Change-Id: I3821336758b13051e9b331b8feb73fb1f8f1184a
fix a "bug" in that the flake8 configuration in tox.ini was exclusively
selecting H231 as the only error it would report, so it was missing the
errors in the python modules (such as submit_log_processor_jobs). Due to
this being the case for a long time (since 2004) limit the more thorough
linting to the roles/ and playbooks/ directories where we'll be adding
ansible plugins/modules/etc. Also, lint in jenkins/script and nodepool.
Fix problems found.
We can lint everything with pep8 once the zuul v2 scripts are removed,
not worth patching them right now.
Change-Id: I479f010643cf3b67c183d763510f07a33400d38b
Co-Authored-By: Jesse Keating <omgjlk@us.ibm.com>
We overlooked setting up the proper permission on both our
initialize-urandom python and systemd scripts.
Change-Id: I6da27a049954961c9333ebeb48382f8b175dc2d9
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
In our Xenial images, we see unbound take a while to start because
it uses openssl which uses the getrandom call which can block during
early boot if the nonblocking random number generator is not yet
initialized.
This script uses haveged to quickly initialize the generator.
This commit only includes the script, a later commit will add the
rest of the necessary install steps to the element.
Change-Id: I09d18a0bad6c380fd149660ebfdaf6c12730dc74
