Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
Using these macros for deployment jobs will report the deployment
results of Fuel to the testresults database[1].
[1] http://testresults.opnfv.org/test/#/deployresults
Change-Id: I353631f073578b4a2da0f08ffba4042931e65dca
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
Commit 33073c5a3426c1867411db446bc9e5d84d2a7747 ("jjb: xci:
xci-run-functest.sh: Ensure env vars are quoted during reload") added
support for reloading the OPNFV host environment in a safe way but that
didn't work because the internal '$var' variable was not escaped so it
was evaluated on the local host instead of the remote one. This fixes
the problem by properly escaping the variable.
Change-Id: I7c90ae18f77aca076579f70c7c0e9a72aaaad7c8
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
The output of the 'env' command does not use quotes when printing the
env variables so trying to source the xci.env file will lead to problems like
the following one:
/home/devuser/releng-xci/.cache/xci.env: line 17: PROFILEREAD: readonly variable
/home/devuser/releng-xci/.cache/xci.env: line 20: 50340: command not found
/home/devuser/releng-xci/.cache/xci.env: line 40: controller00: command not found
/home/devuser/releng-xci/.cache/xci.env: line 48: on: command not found
/home/devuser/releng-xci/.cache/xci.env: line 55: Francisco/O=IT/CN=xci.releng.opnfv.org: No such file or directory
/home/devuser/releng-xci/.cache/xci.env: line 75: a: command not found
/home/devuser/releng-xci/.cache/xci.env: line 88: -I: command not found
/home/devuser/releng-xci/.cache/xci.env: line 90: 50340: command not found
/home/devuser/releng-xci/.cache/xci.env: line 92: -e: command not found
/home/devuser/releng-xci/.cache/xci.env: line 95: fg: no job control
/home/devuser/releng-xci/.cache/xci.env: line 101: fg: no job control
As such, we need to ensure that variables are properly quoted when
exported.
Change-Id: Ie98d8c921bae849d6bffd3858f67708f417b1d0f
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
|
|
|
|
Temporary disable master branch job on zte-pod2 to make room
for Fraser branch job.
Change-Id: I9f2eea0e1c85eab741f80e6db6b773eec71c39f1
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
|
|
The jobs are unmaintained and broken for months. Upstream already has
jobs for all 3 distributions so there is little value to test a similar
scenario on the OPNFV side. As such, lets disable them and save some
hardware resources for XCI.
Change-Id: I0ab7d51f44bdeb6f630671e8d05dd2baf67d756c
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Use these scenario which can trigger doctor jobs running in functest
Change-Id: I66df099c3923b9c47aab9f9f8685052bd33331f7
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
We only set default scenario if there is not one set already so we
need to check if the array is empty.
Change-Id: Ic5019fb68349adaf52d669aed43574bc5eaeddc3
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Change-Id: I9576417cd2c47fd10153d841dddb334cb47c666e
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Currently doctor job uses multiple 'multijob' in builders to
virify tests in different installers, these multijobs run in sequentially
which will cost a long time. These jobs are not related to each other in
different installer.
Change-Id: Idce03920ec6244a9ce288c940a24d0707af1a694
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
Change-Id: If5b4dfaef431570f65a321209a4fa4c94292d89f
Signed-off-by: Yibo Cai <yibo.cai@arm.com>
|
|
Change-Id: Ibd6a523aa9da3aa6c2622a5f183102ffdbc3ccb8
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I167bbea911fb3aee6fa21b7ff28b18d7fae61bb9
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I0a5a6d584b3740d88dc4f342ffc1d107962762e6
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: Icf57ec3e65e391207333bb8780ea215bcf4434a4
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I21c5ab27243bd50dee76d8b10c10ae0fb8aa5f1d
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
|
|
|
|
Domino is not in the fraser release.
This is part of a cleanup to remove euphrates jobs
Change-Id: Ica789accd0148cf847c3498d151bd8ae0b59e8bd
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I63fdf2826d2077465f264f082dc1a15eafc2b05a
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I5e5f66b1226291934fecca6fcf83dd649fb82f0e
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: Idbe3be3da5ddf0fb9b1649002d7cf6bd8babc817
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I8a223d7f9a0458f9cc01a2fedcb630b711b4465f
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
|
|
These have been moved back into installer-params.yml and added to the
daisy jobs where 'testapi-parameters' is being used.
Including this in the list of parameters would cause duplication as most
installers already include 'DEPLOY_SCENARIO' as a parameter. The
'DEPLOY_SCENARIO' parameter is also sometimes defined through a macro,
which could cause second declaration of DEPLOY_SCENARIO (defaulting to
'os-nosdn-nofeature-ha') to always be used.
Documentation has been added to the parameter to explain the related
macros and how they should be used.
Change-Id: I9aef031dbcf523ae2db15695ce294bd85025530d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
The wrong job name was being triggered so no job was running to collect
logs.
Change-Id: Ib58b030ac24920fc7906bff92a481407587a39bf
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I761ec6f28ab4b2d7dc47250d49730dbe302221e0
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
|
|
|
|
We should reload the XCI environment before running functest in order to
ensure that playbooks have the correct information from the XCI
deployment.
Change-Id: Ieadeca61d3ea3e504e21aa96945ad067f20d1489
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
|
|
JIRA: QTIP-297
Change-Id: Ie3002ab4eae57d79d0edeb9c39c2ab273c5c3915
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
|
|
This change enables Functest for kubernetes scenarios but any change
that impacts kubernetes scenarios will fail and block the change from
merging until the prepare-functest playbook and role are fixed in
releng-xci.
Change-Id: I046e3a0fb9a211cf9d629899017922288d466b0c
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Functest Euphrates is now EOL (jjobs creating containers has already
been removed)
Change-Id: I668137b2701d073ce95856fa20dc54135a6cc111
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Change-Id: I6b35a5b36b1cc7b8ce2298388b9bb5caf9e44fc9
|
|
Commands may exit with non-zero exit code but this could be normal (for
example grep does than when it doesn't match anything). As such, lets
not fail on everything but rather capture such failures and handle them
appropriately.
Change-Id: Icc16d0ccd09fd6f262600ae514161bfdf0c593f1
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
As part of our new XCI effort, we only enable upstream ODL scenarios
initially.
Change-Id: I737bbffce14b6c5c69dfbbb653659c7e693cb4fb
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|