Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
Change-Id: I216d1877cba73272bbb37bf84c74dbf77dc2952d
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: I8e88ab0598f43be8d0c9c4ad199dba91c1561f13
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: Ib97cee06438d4ac240c55b0b504338f435a68259
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: Iebd8a9b558486927c25735d266d3557f91e26a15
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: Ib61cb40b04eed23ad276f261645d83ce7cf00629
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Functest has multiplied the testcases and integrates several ones
which are growing (e.g. snaps).
4 hours is reached if snaps or one vnf testcase fails (20 minutes).
https://build.opnfv.org/ci/view/functest/job/functest-compass-baremetal-daily-master/1695/console
Change-Id: I5e8b744d35b5253f6e7ac1310286ae374de1943b
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
|
|
When [1] is merged, prepare_env won't exist and the call
will fail. Keeps the former call until Euphrates jobs
are stopped.
[1] https://gerrit.opnfv.org/gerrit/#/c/47267/
Change-Id: Ia41906f9e8ee15409cb28bb9bb621a7ab1964eee
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
Change-Id: I3e9d8122bf67296d6270583efeda34ac64e21e68
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: I2de88bcf0407b89579447159ed0ed233fbd62553
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
This patch also removes the --report flag when running a single
test case (functest-suite type of jobs)
Change-Id: Ic94fba53ced7c6f908905c02577e1b104f15afb7
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
There is a former job template which was used for testing Alpine
containers at the beginning on 2 alpine-pods. That is not needed
any longer since we are running Alpine everywhere.
Also, this patch re-orders the builders.
Change-Id: Iabb41552f513773ebae1170232b8db1aeceb9a59
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
Now the job functest-daisy-baremetal-daily-master runs on zte-pod3,
but the INSTALLER_IP in [1] belongs to zte-pod2.
Use virsh and arp commands to get the real INSTALLER_IP.
[1] https://build.opnfv.org/ci/view/functest/job/functest-daisy-baremetal-daily-master/151/console
Change-Id: I9e297b8f7a240437f81b4c3e2eab5949ac9d5e51
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
JIRA: RELENG-254
Change-Id: I89043a1149360d587588e8c887f88cc5192c1692
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
This will allow the push-test-logs.sh script to be executed
in any case instead of exiting directly
Change-Id: I03c40e2f368485389a21313f98745217ae634eca
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
It was used in Danube and there are no more Functest jobs
that are runnign stable/danube branch.
Change-Id: If297487767e8e8ead39aa4a10f58c6554be197b0
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
It was used in Danube and there are no more Functest jobs
that are runnign stable/danube branch.
Change-Id: I8e8b1f769b76ad511af6086b7a21dd9ae94404f0
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
|
|
Change-Id: I8a8d46798ea73364cf0f2b66464d3628d6d572d3
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
|
|
Change-Id: I3ec48bd337f8dc9100ff82f53067954925245dfa
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Replace single by double quotes, variables should
be within double quotes.
Change-Id: I5dae42178f5638689a8c46e03a01c12bd42b65e1
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
Change-Id: I182962570fc88e181f312ad432daf774b79e44f1
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: I1bb751e1df37bb00347f5597c95066041b37ead2
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
|
|
Change-Id: I40e00a1abfc383bb5f13a8ec140294d3a67e5cbf
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
And add debug information for the suite jobs
Change-Id: I478a09c689b54f82246a72c19726576ff5aeaffd
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
Also, improve suite job with alpine images.
Change-Id: I1367dea6b09361641c38ef91652acec5be4fbebb
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: I8c0c088c5b6879033e1d369488b589271e741a68
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Updated all the jobs that use functest-suite.
For single test cases, we need to know to which docker image
the test belongs to.
Change-Id: If7db231ccc891233423f2f2bc3aa5b95d048b30a
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
So far we had 2 approaches:
* return Functest CI status: can be OK even if tests are FAIL
* return Functest Test status: can be FAIL even if all Functest tests are OK
(Fail in onboaraded tests)
A 3rd way is possible thanks to [1].
We consider only Functest status and Functest tests for the return statement
the return will be FAIL only if
* error in the framework
* error in Functest Tests
So concretely, if promise, Doctor can be FAIL, if Functest tests are OK, the
return will be PASS
[1]: https://gerrit.opnfv.org/gerrit/#/c/42245/
Change-Id: I6c7fbe99d888e43700ddb2dfc9bfd6cc9bfbaed6
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Change-Id: I536d3182ef7f4b598f734502cc0880201487d968
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This change switches jobs to euphrates and removes danube jobs.
Change-Id: I9e53c595886b6214927c10c380a898e3c7510c7b
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
Enable parser project since it has tested successfully in multiple
installers.
Change-Id: I7f6f22910cf2b44975c511d3ff20b822181c18fe
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
|
|
VNF test cases take long time when executed in
virtual deployments, mainly due to the resources
assigned to the virtual hosts.
Change-Id: Id0591e6217515b04fe163488a89667ac66c06cdd
Signed-off-by: JoseLausuch <lausso@Joses-iMac.local>
|
|
regression reported by barometer project
1) --privileged=true no more set in docker run
2) wrong INSTALLER_IP -e INSTALLER_IP=192.168.122.169
3) ssh_key no more mounted -v /root/.ssh/id_rsa:/root/.ssh/id_rsa
Change-Id: Iccda9d57b7ea4c346ff26e9b2f74320bfe7eec95
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Read compute architecture form salt master and send it as
environment variable.
JIRA: ARMBAND-310
Change-Id: I5c44697d1856f4d09df6fbbbf23ec94478e08f21
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Change-Id: Ie7e8228dc4316a70c8cd800415108180148f5f31
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Change-Id: I1e72cb5b7ce9441900a239bb593d89275fe7b675
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Functest Alpine not supported yet for aarch64 architecture.
Task for Armband project but until support could be done, the
traditionnal docker shall be used for armband tests
usage of alpine leads to errors [1]
[1]: https://build.opnfv.org/ci/view/functest/job/functest-fuel-armband-baremetal-daily-master/214/console
Change-Id: I48e05a0c7cd97989784fd97348bd331425c4877e
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Change-Id: If6d4f6b2ac0266af35b150159a752b8b6f48ad83
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Fuel@OPNFV mcpcontrol network (equiv to old admin/PXE net) has been
configured to use 192.168.10.0/24 during E release cycle.
However, due to overlapping with Ericsson-pod1 networks, we decided
to re-use the old CIDR Fuel used before E release (10.20.0.0/24).
This allows reusing the INSTALLER_IP param instead of recently added
SALT_MASTER_IP param.
Current change refactors all usage of SALT_MASTER_IP in favor of old
INSTALLER_IP, thus reducing complexity and providing a familiar env
to leagcy Fuel users.
JIRA: FUEL-285
Change-Id: I1e89cca08ce4cb9bf3a82a06043c91ee26aa0794
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
The following alpine containers will be launched one after the others:
- healthcheck
- smoke
- features
- vnf
Old container is kept for suite (which could be refactored later)
Jenkins exit condition (return_value) and push_test_logs to be checkeded.
Regarding the return condition, I did not reapply the mechanism that returns false
when one of the test suite is FAIL. This was misleading for lots of people as
for them, red means functest is FAIL.The argument was, if functest jenkins status
is blue, people believe that tests are PASS and do not consider the results, which
may be FAIL, which may be also misleading...
Due to the refactoring I think we can be more Functest Centric and consider
that if we succeeded in running the test, our CI status shall be PASS (same
behavior than other test projects..HA test FAIL in yardstick do not prevent blue
status).
Scenario owner must have a look at the reportign page to get more details.
Functest PASS means that tests have been succesfully launched, so they know that
there are available results
To summarize
previously Functest OK but 1 or more tests FAIL => red status in Jenkins
currently Functest OK but 1 or more tests FAIL => blue status in Jenkins
Regarding the push to artifacts, it should be transparent (volume) but the last
log links listed on huawei-virtual5 are broken [1]
[1]: https://build.opnfv.org/ci/view/functest/job/functest-alpine-compass-huawei-virtual5-daily-master/27/consoleFull
Change-Id: I4ed036dda3daae3d46726e5946f9d04897bab9bb
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
Temporary solutions relied on ollivier/functest-* but
now opnfv/functest-* are well produced and can be used as official
reference for CI
Change-Id: I02b5a03929d5b31df0db2a6c4722edf62b920df9
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Change-Id: I3b62e855be9205326fee1fa8b2b56cb2276c689c
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|