FIPS needs to be enabled before test-setup is run, as enabling
FIPS requires the node to be rebooted, test-setup needs to run and
setup the environment after the reboot.
Change-Id: I6fecb9c6e917d1a36b2b82c1b02098eed4323ac7
This patch adds a new multinode job definition that enables
FIPS mode prior to multinode configuration.
In order to enable FIPS mode, the OS boot procedure need to be
changed to enable the appropriate kernel flag. This modification
has effect only after system reboot.
The default behavior of this job is to always enable FIPS mode.
Change-Id: I6f1365837d9ed2ba82c391a20f9094c9ef0e6c4e
Signed-off-by: Douglas Viroel <dviroel@redhat.com>
Don't use a shell builtin: shell builtins aren't available since
'command' ansible module is used. Instead, fail with an explicit
error when the required test_command variable is not set.
Fix this error:
Ansible output: b'failed: [host] (item=exit 1) => {
"ansible_loop_var": "item",
"changed": false,
"cmd": "exit 1",
"item": "exit 1",
"msg": "[Errno 2] No such file or directory: 'exit': 'exit'",
"rc": 2
}
Change-Id: I88303f7302d7354ffc8b18e607b28349a9860a57
The job was relying on a security hole to execute untrusted command
on the executor (localhost). This change prevents failure after the
hole is fixed.
Change-Id: I910fb6e6a2659e77991111c8ce5a6b763556aeec
To make it so that a repo can host a simple command which is an
integration test of multiple projects, add the semi-standard
zuul_work_dir variable to the job.
Change-Id: I265469ac9c12c3a38a11b243f3ff747d27141f21
Jobs in this repo should never specify 'base' as their parent,
they should rely on the default tenant base job (which may or
may not be named base).
Change-Id: I6faa085611eca5ce9650b67e975548574773c524
We have too many jobs to put them all in one file; split them up
in files which mirror the documentation.
Change-Id: Ic44f18085ccf0b561a0f4aa0a4274fe8eb99402c
