summaryrefslogtreecommitdiffstats
path: root/doctor_tests
AgeCommit message (Collapse)AuthorFilesLines
2018-12-18remove to set ceilometer config in MCPdongwenjuan1-17/+0
As Mcp already set the notifier for alarm in ceilometer configuration, we remove the configuration workaround. JIRA: DOCTOR-132 Change-Id: I30603d7f364fbbed143ebdb3dc6fdf71b10434a0 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-11-22Merge "Support Fenix and sample implementation accordingly"wenjuan dong8-141/+197
2018-11-20Merge "fix the configparser for Python 2 and 3 Compatibility"Tomi Juvonen1-3/+3
2018-11-19Support Fenix and sample implementation accordinglyTomi Juvonen8-141/+197
Fenix has now same capability as our sample implementation. We can now support Fenix if manually installed on controllers. Sample implementation should be closer to Fenix as Fenix is the place to define the generic interfaces at the end. JIRA: DOCTOR-131 Change-Id: Ied58b8f469dbcc4bb5caa787e62c1831a211ecd6 Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-10-29Fix SSH client connection resetTomi Juvonen1-11/+30
SSH connection might be reseted with long running session. This may happen if run "testcase=all" Change-Id: I232ae906628411dfbe0bbdbdc8d4fb43167760fd Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-10-27fix the configparser for Python 2 and 3 Compatibilitydongwenjuan1-3/+3
Change-Id: I6ea9c031a8093d7ce94b49575cb6bfe348eb6c9a Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-10-25Merge "Support Apex with services in containers"Tomi Juvonen14-116/+314
2018-10-25Support Apex with services in containersTomi Juvonen14-117/+316
Upstream apex now works in containers, so if used, it needs to be supported JIRA: DOCTOR-130 Change-Id: I3d73a1699e4fee53b001f043f55d0eeefa7bfb7b Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-10-25fix the username to login undercloud in Apexdongwenjuan4-8/+9
Change-Id: I6d5325166db642b3481a0327f518ec821a8ab378 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-09-18Merge "delete doctor datasource in congress when cleanup"wenjuan dong1-6/+13
2018-09-18run profile even the notification time is larger than 1Sdongwenjuan1-0/+4
Change-Id: Ide5ff5e1c894e3144ac07f14b76b7092539d39f6 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-09-18delete doctor datasource in congress when cleanupdongwenjuan1-6/+13
If we delete doctor driver in congress configuration when cleanup, the doctor datasource still existed, it will be raise an exeption in congress server and the service can't be started. Change-Id: Icefde9964229ef3d55af09cc2e81680cb8d19813 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-08-23bugfix: add doctor datasource in congressdongwenjuan6-84/+111
Change-Id: I465fd6c59daf99dd543488a15819dab78e8cdd7b Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-08-09Add maintenance test codeTomi Juvonen11-11/+1259
-Add sample admin_tool -Add sample app_manager -Modify sample inspector JIRA: DOCTOR-106 Change-Id: I52cffecaa88452ce5e7cc6487534c88fcfd378ad Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-08-09Add setup and cleanup for maintenance testTomi Juvonen13-91/+734
JIRA: DOCTOR-106 Change-Id: Idb95e1391e8f9094f68e2c7bc79fd2d7e01af9de Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-08-09Merge "bugfix: kill the stunnel when cleanup"Tomi Juvonen1-3/+2
2018-08-09Merge "add ssh_keyfile for connect to installer in Apex"wenjuan dong3-1/+7
2018-08-09bugfix: kill the stunnel when cleanupdongwenjuan1-3/+2
Popen.terminate() will kill the child process, but if you set the shell argument to True, this is the process ID of the spawned shell, so the stunnels are still exit.It will cause the failure of stunnel setup in the next test runtime. see: https://stackoverflow.com/questions/4789837/how-to-terminate-a-python-subprocess-launched-with-shell-true/4791612#4791612 Change-Id: I578611510f5bd1eb0dbd9a08ab408ccf101594f7 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-08-07enlarge the time of link downdongwenjuan2-2/+2
Change-Id: I063d7ba9b3eb8999cb2b08e7c6deca2644eb169e Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-08-03bugfix: fix the filename of ssh tunneldongwenjuan1-1/+1
The stunnel will be setup failed in the docker if we have the .log at the end of file name. Change-Id: I272a9fa3b668d49b0e26752403ad41a67dcfedc7 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-08-01add ssh_keyfile for connect to installer in Apexdongwenjuan3-1/+7
Change-Id: I8809a24e75c0260f67d3e128b8bbd1becf924529 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-06-08[consumer] fix default value for port numberRyota MIBU1-1/+1
Port number of consumer should be int instead of str. Change-Id: I7f7c7b23ede094d1d3278ef4cd5f971fb57ca2e8 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2018-04-23bugfix: certificate for https for MCP in baremetaldongwenjuan1-1/+2
In Mcp baremetal env, doctor test is always failed because of ssl certificate for https. Change-Id: Ia443c6463fe177ff4e1ab5a86429750fbd23740c Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-04-12get 'test_case' option form environment variabledongwenjuan1-1/+4
Get 'test_case' option form environment variable. If no environment variable, use the default value so that we can specify the test case in doctor verify job. Change-Id: I1bc25d024ca56637d779006d685b57254af355a5 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-03-28Merge "support MCP installer"Bertrand Souville5-133/+198
2018-03-20optimize the fault notification testdongwenjuan10-253/+277
Change-Id: I47572b4515049c49f9aa04bf7984757779a605f3 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-03-20support MCP installerdongwenjuan5-133/+198
1.support MCP installer 2.optimize the installer code JIRA: DOCTOR-121 Change-Id: I8675c2652944575a8f73d0d1e2dafaad5a3e88e3 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-03-07Removing temporary process group solution.Tomi Juvonen2-8/+1
Introducing root cause fix for sample inspector shutdown JIRA: DOCTOR-123 Change-Id: Ibc95d482f476b60584c224d8e2757d071149d611 Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-02-20At least APEX will not work with Fraser if we do not wait 120 sec for AODHTomi Juvonen1-1/+2
Change-Id: I4e3e510f51258e892b467f819951bd1a98625f90 Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-02-14Add process group so can kill possible hanging subprocesses.Tomi Juvonen1-15/+20
This should be workaround before actual fix is done. JIRA: DOCTOR-123 Change-Id: I70fd4ed9d2aa2cc3a6c46e2515062b7acd31ca0a Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-01-23create flavor for Apex installerdongwenjuan3-10/+12
As doctor functest CI runs failed in Apex installer, it indicates that flavor is None. See http://artifacts.opnfv.org/logs/functest/lf-pod1/2018-01-21_05-30-00/doctor-notification.log Change-Id: Ia7a7111a7c6b94864f2e12f30969fe6e411058af Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-01-15change test_case optionRyota MIBU2-3/+14
This patch changes the way to specify target test case to be run, 'test_fault_management' --> 'fault_management'. Also, the default is set to 'fault_management'. The reason to this is not to block any other on-going activities for Fraser release. Change-Id: I92305477a84ffa0e703c36d309fbdf97435782aa Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2018-01-15Merge "fix the pep8 check"Ryota Mibu2-9/+14
2018-01-15fix the pep8 checkdongwenjuan2-9/+14
Change-Id: I91b8b6cd07d859a1d1abdc25f015a3c3b2756fab Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-01-12ability to run maintenance testTomi Juvonen3-16/+71
JIRA: DOCTOR-119 Change-Id: I98e556fba30eb7ba244cb9d0d88a9e95c39193ff Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-01-09Merge "support pep8 check"Ryota Mibu26-159/+254
2018-01-09Merge "fix the CI error"Tomi Juvonen1-4/+8
2018-01-09fix the CI errordongwenjuan1-4/+8
Change-Id: I0b60e6f1e15cbe556c7555186352d28490b98acc Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-01-09support pep8 checkdongwenjuan26-159/+254
Change-Id: I3c4358694c57d27a207ae60712c44f717c8895f7 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-01-08support daisy installerdongwenjuan3-4/+111
JIRA: DOCTOR-118 Change-Id: Id4d586fd2b7ca043cfd8231b9c46bdc581f039ab Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2017-12-21use keystone v3 APIdongwenjuan4-27/+58
Change-Id: Ia642279a99ad9bf014764337c8a5170e3c98e2f2 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2017-12-11support vitrage inspector for local installerdongwenjuan8-24/+178
JIRA: DOCTOR-122 Change-Id: I771f778767a204e809d892c70603e479c1ed2f5c Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2017-10-16fix the bug for consumer don't receive the notificationdongwenjuan2-3/+1
There is no 'sudo' command in functest container, so the stunnel is setup failed. Change-Id: I9e317c0643a370fb5b35d90363b0ff734a77c040 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2017-10-09fix to get logfiledongwenjuan5-20/+40
Change-Id: I44cc6c5108eb48191ca36cbcb44f787ea542f3ce Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2017-10-06Fix retrieval of log filename pathCarlos Goncalves2-9/+7
Change-Id: I0dd61a020827e7ba9ec7a2e0300bf50dd7175e86 Signed-off-by: Carlos Goncalves <mail@cgoncalves.pt>
2017-10-04Merge "fix the way to get log filename"Ryota Mibu2-12/+10
2017-10-04fix the way to get log filenameRyota MIBU2-12/+10
Change-Id: I9ce494c408c99e1a76a6b485db29a72c3134e487 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2017-10-02fix referring neutron option in inspectorRyota MIBU1-3/+3
Change-Id: I01173cdf301f168edebfc2ec6df82b015adebca7 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2017-09-29option: "update_neutron_port_dp_status"Ryota MIBU2-3/+10
This patch introduces new boolean option "update_neutron_port_dp_status", which disabled by default. Change-Id: Iaf7503d5854251fabf816b9bf3fcc1964c231a68 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2017-09-26fix the path of log filedongwenjuan2-5/+8
Change-Id: I823bdc453c32decb0160f0915d749af4ac664908 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>