The command module doesn't understand the pipefail setting used for
piping a response to the rfs-sync setup script.
Change-Id: Ifb1e70d47f312f44abd603f21ce6fbf8733d9dc4
This patch adds support for installing the latest Security World client
software. The installation media format for that version is a zipped
file containing an ISO.
The mechanism for installing the source media was changed to expect this
new format. The file is still downloaded to the target host and now
unzip is used instead of tar to unarchive the ISO.
The client software is now installed on the target host using the RPM files
found in the ISO image.
Change-Id: If00a8612cd50f492da833033a2ed3256585617bd
The tox option to skip source distribution building is skipsdist,
but this seems to be often misspelled skipdist instead, which gets
silently ignored and so does not take effect. Correct it
everywhere, in hopes that new projects will finally stop copying
this mistake around.
See https://tox.readthedocs.io/en/latest/config.html#conf-skipsdist
and https://github.com/tox-dev/tox/issues/1388 for details.
Change-Id: I9b7768fdb4e8865648da1c697fa16ee2d1a9c604
With setuptools release 61.0.0 ansible-role-thales-hsm's package build
command (python3 setup.py sdist bdist_wheel) started to fail:
error: Multiple top-level packages discovered in a flat-layout:
['files', 'defaults', 'handlers', 'templates', 'releasenotes'].
This bug is mentioned in setuptools issue 3197 [1], and the suggested
workaround is to disable auto-discovery by adding 'py_modules=[]' in
setup.py.
ansible-lint also released a new version (6.0.0), which has new rules
that blocks the gate. As a workaround, this patch caps ansible-lint
version <6.0.0 to unblock the gate.
[1] https://github.com/pypa/setuptools/issues/3197
Change-Id: Idb765d09f9498bc13f952c055026e29a46cab8d3
A change was introduced to TripleO Heat Templates [1]
to expect roles to use underscores instead of dashes in
the directory name.
[1] https://review.opendev.org/#/c/713792/
Change-Id: I61ee17f7e00e4a5bab5b6b44beb8ea92a93a8058
After we set up synchronization with the RFS server, we should
immediately do a sync to make sure the local keystore matches
the RFS server.
Change-Id: Ib5926776aafbb7615ea8d22386fc33c520e29506