Age | Commit message (Collapse) | Author | Files | Lines |
|
argument refactoring for main and init
functions in generate_reports
Change-Id: I291d04a9c0ed381f4b92e989270c0b9a37c15264
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
(cherry picked from commit cc72b61456aeaa9752527d55541df3791ff1fbbf)
|
|
Change-Id: I5cd900cee809b8fd935a5c8b862a9ecd6278bdf5
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
(cherry picked from commit 0077ad99834d51654a75a5ccf49fcfcaf828b905)
|
|
Change-Id: I66f43fb09472948bc71178cd8aeb14dc1ab5fa55
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
(cherry picked from commit f651565ffc8979ef99a1d9bc001561bf1fba3779)
|
|
So far DB url was retrieved from configuration file
If you want to use the CI chain (jenkins, testapi, test DB,
functest, ..) then you have a problem
calling functest will systematically point to the configuration
from the repo
Supporting env variable allow to avoid post processing in the
configuration file and as a consequence offer the possibility
to create a local DB to host local results
Change-Id: Ie64b8b265827d7f5724c7066a8c173de8cf012e2
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
(cherry picked from commit 0c194ede4dd9eb46b61af49e85527fcc368a8fca)
|
|
ovno has no danube branch and is not used
clean the ovno from functest to avoid side effect
when producing danube functest docker file
Change-Id: I5347111fc90a04ca9018679b5578ca30ae33b2f2
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
(cherry picked from commit 65b26f2e9db7e0cf336c147d46d91cb1c828a67b)
|
|
Change-Id: I774d3625d35e3d264d609ba9aa7538a723923bcf
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
(cherry picked from commit 1ee860c3f5391234e5424b49e5e9cba9cdebf593)
|
|
Actually attach_detach_volume must be skipped because the device name
ain't reliable and that's using a hard-coded device name in config.
This test should just get the device info after the attach and use
that rather than the hard-coded config option in Tempest that ain't
likely to work - the test should have been written more dynamically.
However, set volume device name to "vdc" since "vdb" is used for config
drive when force_config_drive=True is in action.
Change-Id: Ic70de93a609df932c7749a94f71505e927df1b79
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
(cherry picked from commit 3b006a6a3742325c0fe4ccc557b7a8e140f2cab2)
|
|
|
|
Change-Id: I43550b2062c69d7b4eb144057a90806f92328739
Signed-off-by: boucherv <valentin.boucher@orange.com>
|
|
|
|
|
|
|
|
Change-Id: I25423cc3fbab54f81047fbebd0bc33895d826186
Signed-off-by: boucherv <valentin.boucher@orange.com>
|
|
Doctor feature not available for Joid on Danube
Change-Id: I1d39ff15a1fe003689828f6923b92c7e7c7d716f
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
Change-Id: Ibf04adcaa0b14c4cdda8fba2ef2826a0c7f3b7d4
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
|
|
|
|
|
|
|
|
Change-Id: If92c7d402b88f59367564f7279d426eb8f3b582a
Signed-off-by: boucherv <valentin.boucher@orange.com>
|
|
currently the snaps healthcheck (dhcp) is tried first
it should be connectivity, api, dhcp
the reporting looks for scenario based on connectivity
testing dhcp first => scenarios ok on connectivy but
failed with DHCP are not considered, which could be
misleading
Change-Id: I0eb34b1f5ba163540281e5ef0dcb12c8cefa88bd
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
JIRA: FUNCTEST-747
Change-Id: I85f15188315136cc44876914325e3693f7973af8
Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
|
|
|
|
Added:
- fds repository to docker file
- fds test to smoke tier in testcases
- config values for fds tests
A new robot var OS_AUTH_URL is defined as expected by FDS robot files.
Method args switch from Keystone IP to OS_AUTH_URL which is more
precised. The argument parsing is changed too.
Co-Authored-By: Cédric Ollivier <cedric.ollivier@orange.com>
Change-Id: Ife27ab4a83f0110cbdcf7c9d47d9b3fb4c0ec705
Signed-off-by: Tomas Cechvala <tcechval@cisco.com>
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
|
|
This reverts commit 044de9eb0c74fb2ef9cb34b6487bf0536412058d.
Change-Id: I9179f4b5ce866456e8ec85cb8a730a5d7f2af16e
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
|
|
|
|
not need to clone full releng
depth 1 is enough
do not go out of workspace anymore..never...
Change-Id: I1d2dbc30bec6c168ef7ddf3327cb00fff4056aa1
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Change-Id: Id903683b12366c5a2f486c8b7d7ce6977d4448e0
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
JIRA: FUNCTEST-742
Change-Id: I5de8ed22932250c542751e38eae3185c4a263cd0
Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
|
|
Change-Id: Ied92224bc80ab4e02611e7b1f4bf33f276914e89
Signed-off-by: boucherv <valentin.boucher@orange.com>
|
|
This commit sends the aarch64 custom config to the snaps integration
tests. Since these are the same as the snaps healthcheck, no additional
values were added to config_aarch64_patch.yaml
Change-Id: I5f2302a3c65d47ec8fca661888268489e2c6ba35
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Labels serve as anchors/ refs when referenced from other documents
This patch adds labels to docs/*/*/index.rst
Change-Id: Iaa339f0f8b2efbde286b173ae6cf7e92cddab115
Signed-off-by: ShubhamRathi <shubhamiiitbackup@gmail.com>
|
|
SNAPS healthcheck is already excluded due to the
use of QCOW2 images, not compatible with lxd
scenarios
2 JIRAs have been cretaed to adapt the SNAPS cases
to lxd in Euphrates
https://jira.opnfv.org/browse/FUNCTEST-752
https://jira.opnfv.org/browse/FUNCTEST-753
Additionnal cleaning done on testcases.yaml
- remove juju_epc case (no one from OAI available
for Danube)
- remove orchestra (as standalone test case of the
MANO stack, postponed to Euphrates)
- comment aaa (empty sample used to illustrate
the VNF abstraction but not completed for Danube)
Change-Id: Ibad6cad4c92ee9897b6665b29c09b62cb1986aae
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
As certain scenarios such as, DPDK, FDIO, and OVS use cases
require special 'hw:' settings to flavors, SNAPS-OO has just
implemented the ability to take in these configuration values
to apply to its integration tests. This change checks the
scenario and should be configuring the flavor metadata accordingly.
Also see SNAPS-38
Used this as an opportunity to refactor the SNAPS test classes as well...
JIRA: FUNCTEST-746
Change-Id: I63535776acde088a7461f602966a324b6207592d
Signed-off-by: spisarski <s.pisarski@cablelabs.com>
|
|
JIRA: FUNCTEST-750
1.Modification of repo path for vrouter in config_functest.yaml
Change-Id: I798e27df9667c3dea55dddba51c53f6ac0d13381
Signed-off-by: Hideyasu Hayashi <hideyasu.hayashi@okinawaopenlabs.org>
|
|
Functest verify job failed due to that test_prepare_env.py mistook one
function of ft_utils.execute_command_raise.
Change-Id: Ib3b8ca807308bf5c6d250e7debb4c9e1e106e3d1
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
|
|
|
|
|
|
delete no longer used ft_constants in run_test.py
substitute ft_constants with CONST in foundation.py and remove useless
str()
finally delete not-used file functest_constants.py
Change-Id: I109a5409e501b610f41aae7d75c55ca745a3d4c1
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
|
|
This commit is half of the fix for adapting the snaps healthcheck
to run on an aarch64 POD. The fix consists in reading the custom
parameters and passing them to the snaps test
The snaps part that uses this info is
https://gerrit.opnfv.org/gerrit/29853
JIRA: ARMBAND-222
Change-Id: I2027f2ef3afe0caddef781771f2190fc173aff8c
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Change-Id: I2bf68a31e581b2a80785f1b13380a28d5bf84d80
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Change-Id: If7b656007ae0c8aa47fb12b10c49517fc0044750
Signed-off-by: boucherv <valentin.boucher@orange.com>
|
|
|