Age | Commit message (Collapse) | Author | Files | Lines |
|
Directories affected:
- ci
- core
and respective unit tests
Change-Id: I6a3d5aa68de29fc5a37ae543a067ff797eba33e6
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
It deletes functest.utils.functest_logger and the related unit tests.
Then it modifies all functest modules to get all loggers via
logging.getLogger(). __name__ is mainly used as getLogger arg as
proposed by logging [1].
All loggers and handlers are now defined via functest/ci/logging.ini
instead of a dict loaded by an external json file.
Now only warn messages and info messages from ci and core packages are
printed in console.
[1] https://docs.python.org/2/library/logging.html
Change-Id: Ic192855e0f9bf94825d8f7ec73549a0f3b8d44c5
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
JIRA: FUNCTEST-764
1. When creating verifier via rally in functest env prepare, without the
parameter "--system-wide", rally will install tempest and its dependent
packages into the virtual env of rally. Thus, it needs to connect internet
when installing tempest, which will not enable functest offline.
2. Some packages are needed for multisite testcase, and they are installed
in virtual env of rally before. But if "--system-wide" is set, there packages
should be installed addtionally.
Change-Id: I340701e9ed4a0f8f278ff952f0dd61470c6deed1
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
The bug was induced by [1]
1. the key try logic is added back
2. the logic of patch_config_file is updated as NoneType error was
thrown
3. refactored the patch_config_file to avoid calling the same function
twice on every type of POD. For non-aarch64, only calling the function
once is enough
[1] https://gerrit.opnfv.org/gerrit/#/c/28945/
Change-Id: I2e9fdc5ac3c04800cfc898ea654ff24e2bdeaef4
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
In order to run functest on an aarch64 POD, some custom configuration
is needed. Up until now that custom configuration was put on the arm
jenkins slave. With this commit it is integrated in functest project.
1. In order to identify if the POD is aarch64 or x86 function
get_arch() from https://gerrit.opnfv.org/gerrit/#/c/29099
is used
2. Changes to config_functest.yaml are made via a new patch file
config_aarch64_patch.yaml which is applied for all scenarios.
Function patch_config_file() is modified to be more generic. It
now receives a file as parameter and merges any type of patch file
3. The aarch64 cirros images are downloaded into the data directory.
Functest can be run from both an aarch64 or a x86 jenkins slave
in order to test an aarch64 POD. So the images are downloded in both
dockerfiles
4. Other custom config needs to be added to /etc/rally/rally.conf
in the docker. The custom config is set in rally_aarch64_patch.conf
and inserted in the needed file before the rally environment is
set up
JIRA: ARMBAND-60
Change-Id: I8e460cdf02d297c259cbbd9c05e7983367fd2bb9
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
|
|
|
|
CI for compass and joid failed as there is no key defined in
installer_params.yaml
Change-Id: I8d17d36d854974c0751d3fd3bab4994205f786bb
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
|
|
JIRA: FUNCTEST-707
Change-Id: Ieaa888375136eddbbe003a24b32bf09fd0f92923
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
JIRA: FUNCTEST-727
Change-Id: I4d8e24c0cb6272d92dc777dc82d56490948598db
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
Example virtual deployment apex:
http://paste.openstack.org/raw/599536/
Example CI POD:
http://paste.openstack.org/raw/599537/
Change-Id: I0711b45a525bc074a9c05f0ea3a194b2db05f2d9
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
This is causing some problems.
https://build.opnfv.org/ci/view/functest/job/functest-fuel-baremetal-daily-master/1121/console
This reverts commit 9886535d617d95e7d2c2f294e79a7cd994fcd685.
Change-Id: I8524dff5deea073f0975df1e712766620002523e
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Example output: http://pastebin.com/raw/xWTe9tAY
Change-Id: Ib8100089318f807fb4d5d4fff2911179eb18216e
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
It also fixes one issue when printing summary for tiers and others
induced by [1].
[1] https://gerrit.opnfv.org/gerrit/#/c/26587/
JIRA: FUNCTEST-438
Co-Authored-By: Cédric Ollivier <cedric.ollivier@orange.com>
Change-Id: I821efaa7d62b208d797d19563f573d1e28da9df4
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
It fixes issues raised when an env var contains '=' (e.g. LS_COLORS).
It now exports the vars listed in rc_file without creating a new
process.
Change-Id: I6e6a4e3ab9c45afe4d40015831acb283acbe564c
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
So far, healthcheck.sh was creating m1.tiny flavor.
We are planning to remove that script and replace it by
SNAPS api and connection check.
Althought, a better approach to this would be that all
the tests create the flavor if needed, but these are the
tests that rely on this flavor:
- vping ssh
- vping userdata
- rally
- tempest
- onos_sfc
Change-Id: I537f68a55d733b24b6b15f5cf3710bca40fbc622
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
JIRA: FUNCTEST-541
Change-Id: Ife04f58dc31ca9ba6316cc31577f81a6bf0e0405
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
|
|
JIRA: FUNCTEST-652
1. Updated the Rally repository to master
the keystone test scenarios of TAG= 0.7.0 cannot run on Newton
also, 0.7.0 is the last tag that exists
2. Update the Tempest installation with updated rally command
Rally team said "there was no possibility to do it in backward
compatible way(rally verify re-design)"
3. The `rally show` was deprecated[1] in the master and corresponding
logic is updated
4. Update rally commands
[1]
https://github.com/openstack/rally/commit/f2fc3015beb4cfd8053db728765714500db6eeb2
Change-Id: Ief9e36a16dd92e4449c0f76579e7191a93aa3e21
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
Can't import run_tests in test_run_tests.py (new unit test file).
It is throwing error: nosetests: error: unrecognized arguments
It is because of declaration of parser and args which are global
in file, So to allow safe import of this file,
we need to declare it into __main__ branch.
Change-Id: Ie11ebcfd8a1b8e692bd8bf4260a54f752b67fd5e
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
|
|
JIRA: FUNCTEST-673
Change-Id: Ia37fb5a08c8fbc4a8acb666565ea887f9ae48b83
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
JIRA: FUNCTEST-675
Change-Id: I342d51391323dd1ffe516d8dbc13b2d543374a3e
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
|
|
JIRA: FUNCTEST-630
Change-Id: I2b6d3bec67c6fe290fb2ad795a54a2dd2e3c7a0b
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
JIRA: FUNCTEST-533
1. Extracted all global variables into functest_constants.py and updated all affected areas accordingly
2. Used os.path.join to replace '/' to come up with the path for better cross-platform support and improve the path accuracy
3. Removed unused variables
4. Updated the hardcoded path in Dockerfile by using variable reference
5. Removed "/" ending from all path variables
6. Updated the unit test
Change-Id: Ib30a81d1f0c83fbaef042d63c187c27bd18301bb
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
JIRA: FUNCTEST-525
Change-Id: I6b09eaec55e42a3ee1474b21bc7ed87a71118e60
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|