diff options
author | Markos Chandras <mchandras@suse.de> | 2018-02-23 14:00:41 +0000 |
---|---|---|
committer | Gerrit Code Review <gerrit@opnfv.org> | 2018-02-23 16:45:55 +0000 |
commit | 2d9697abbee6ec96300320a71aeb69ac88f3bee5 (patch) | |
tree | 3a28c7ad152438402eaf3c15908fd4717f00de1a /docs/submodules/functest | |
parent | 3e90eb4793942e5a97a2d7571bdb28f08c623a96 (diff) |
Update git submodules
* Update docs/submodules/releng-xci from branch 'master'
- xci: scripts: start-new-vm.sh: Disable nested virtualization in clean VM
When using the clean VM for the tests, we will end up with 3 levels of
virtualization when functest is executed (1st level = clean vm, 2nd
level = compute node, 3rd level = functest VMs). This makes the functest
VM terribly slow leading to all sorts of random failures. It appears
that KVM can't handle this case, so we need to switch to the QEMU
interpreter instead which is slower but functional. This only affects
the Jenkins jobs, so deployments on baremetal will still use 2 levels of
nested KVM virtualization which should work fine.
Change-Id: If274129fbf347526982ac4cf577d216173eb4d1b
Signed-off-by: Markos Chandras <mchandras@suse.de>
- xci: scripts: start-new-vm: Set pipefail option
In commit I75a8cb8c05957bb205e63210d6cafaf54d989f32 the 'ts' utility
was added in order to print timestamps for deployment. However, this
breaks the exit code since 'pipefail' was not set so every job was
returning 'success'.
Change-Id: Ia5f47ea96a4a5be9ed0664f5c7100accc30cde51
Signed-off-by: Markos Chandras <mchandras@suse.de>
Diffstat (limited to 'docs/submodules/functest')
0 files changed, 0 insertions, 0 deletions