thanks Brian
it is fine (just tested on casablanca see traces below)
my bad for the template dir, I still do not know how I missed it...
the only adaptations I need to do was due to the facts that robot was looking
for template in a particular directory /robot/..
a symbolic link fixed the issue
I also cloned demo and for the moment I keep only the vFW directory at docker
build to remain as small as possible.
I will update the Master part and add it to the test chain after the health
check and before the End to End tests
/Morgan
2019-03-27 12:25:27,569 - xtesting.ci.run_tests - INFO - Deployment description:
+--------------------------------------+-----------------------------------------------------------------------+
| ENV VAR | VALUE
|
+--------------------------------------+-----------------------------------------------------------------------+
| BUILD_TAG |
gitlab_ci-functest-rancher-baremetal-daily-casablanca-2581818 |
| ENERGY_RECORDER_API_URL |
http://energy.opnfv.fr/resources |
| ENERGY_RECORDER_API_PASSWORD |
|
| CI_LOOP | daily
|
| TEST_DB_URL |
http://onap.api.testresults.opnfv.fr/api/v1/results |
| INSTALLER_TYPE | oom
|
| DEPLOY_SCENARIO |
onap-nofeature-noha |
| ENERGY_RECORDER_API_USER |
|
| NODE_NAME |
onap_casablanca_daily_pod4-OPNFV-oom |
+--------------------------------------+-----------------------------------------------------------------------+
2019-03-27 12:25:27,592 - xtesting.ci.run_tests - INFO - Loading test case
'healthdist'...
2019-03-27 12:25:27,670 - xtesting.ci.run_tests - INFO - Running test case
'healthdist'...
Downloaded:service-Vfw20190327122528-csar.csar
2019-03-27 12:29:28,909 - xtesting.core.robotframework - INFO -
==============================================================================
Health-Check :: Testing ecomp components are available via calls.
==============================================================================
Health Distribution Test | PASS |
------------------------------------------------------------------------------
Health-Check :: Testing ecomp components are available via calls. | PASS |
1 critical test, 1 passed, 0 failed
1 test total, 1 passed, 0 failed
==============================================================================
Output: /var/lib/xtesting/results/healthdist/output.xml
2019-03-27 12:29:29,191 - xtesting.core.robotframework - INFO - Results were
successfully parsed
2019-03-27 12:29:30,765 - xtesting.core.robotframework - INFO - Results were
successfully generated
2019-03-27 12:29:31,146 - xtesting.core.testcase - INFO - The results were
successfully pushed to DB
2019-03-27 12:29:31,147 - xtesting.ci.run_tests - INFO - Test result:
+--------------------+------------------+------------------+----------------+
| TEST CASE | PROJECT | DURATION | RESULT |
+--------------------+------------------+------------------+----------------+
| healthdist | functest | 04:01 | PASS |
+--------------------+------------------+------------------+----------------+
2019-03-27 12:29:31,150 - xtesting.ci.run_tests - INFO - Execution exit value:
Result.EX_OK
Le mardi 26 mars 2019 à 12:54 +0000, FREEMAN, BRIAN D a écrit :
Let me try and respond (let me know if I missed one)
The CSAR name printing out means a successful deployment. I save the CSAR
becuase there are uuid’s in it that can be used for instantiation directly to
SO for vCPE use case but also longer term as a more reliable way for robot to
instantiate when we arent trying to test VID. Selenium API’s are notoriously
flacky due to the way the chrome browser modules works.
1. Demo is cloned and the demo/heat directory is copied into robot so we
have all the VNF heat templates to do tests and demo’s (demo leaves the VNF up,
where as test (ete) tend to delete the VNF after the test is over)
2. Asset templates are in testsuite (you must have missed the link)
* [testsuite.git] / robot / assets / templates / asdc / for the ASDC
one but there are templates for all the PUT/POST actions that robot has to take
3. PUT request
* Looks like data is null so the template didn’t get filled out (or even
pulled from the file system it looks like)
* Basically robot opens up the json template from the assets directory
by path and then does a merge of the dictionary with the template to create the
data payload for the PUT.
* KEYWORD ${resp} = RequestsLibrary . Put Request asdc, ${data_path},
data=${data}, headers=${headers}
Documentation:
Send a PUT request on the session object found using the
Start / End / Elapsed:
20190326 06:02:29.491 / 20190326 06:02:29.579 / 00:00:00.088
4.
06:02:29.578
INFO
Put Request using : alias=asdc,
uri=/onboarding-api/v1.0/vendor-software-products/2f0115777f1146a9814e9a3c858def09/versions/6d6cb8f16d3448f8b2cbbb8ad772a5bf/orchestration-template-candidate/process,
data="", headers={u'Accept': u'application/json', u'Content-Type':
u'application/json', u'USER_ID': u'cs0008', u'X-TransactionId':
u'robot-ete-722903e5-0469-43fe-b177-db1ffe3001eb', u'X-FromAppId':
u'robot-ete'}, allow_redirects=True
5.
06:02:29.579
INFO
${resp} = <Response [417]>
Brian
From: [email protected] <[email protected]> On Behalf Of
Morgan Richomme
Sent: Tuesday, March 26, 2019 6:41 AM
To: FREEMAN, BRIAN D <[email protected]>
Cc: [email protected]
Subject: [onap-discuss] some questions on healthdist test
Hi Brian
I ma currently trying to integrate healthdist in xtesting as I did for the
core/small/medium/full healthcheck so it could be used for gating as part of
the non regression test suites.
I added the testcase in the the docker =>
https://github.com/Orange-OpenSource/xtesting-onap-robot/blob/master/testcases.yaml<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Orange-2DOpenSource_xtesting-2Donap-2Drobot_blob_master_testcases.yaml&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=PvInpzzXGu71bonXT9SKqWaw6Af5vuXqZbAt8yyZ6i0&s=jvuW8nVGjlhN4RTxHvlM-Y7lm6nY8lJSyKC6Qf73XEI&e=>
When I run healthdist directly from the jumphost, it is successful (through the
command /opt/oom/kubernetes/robot/etete-k8s.sh onap healthdist)
Health Distribution Test
Downloaded:service-Vfw20190326100512-csar.csar | PASS |
according to the traces, it is triggered as follow
kubectl --namespace onap exec onap-robot-robot-5b5cbb95fc-tkbzq --
/var/opt/OpenECOMP_ETE/runTags.sh -V /share/config/vm_properties.py -V
/share/config/integration_robot_properties.py -V
/share/config/integration_preload_parameters.py -v GLOBAL_BUILD_NUMBER:5836 -d
/share/logs/0001_ete_healthdist -i healthdist --display 91
So I believed the integration would be relatively straight forward as I already
referenced the 3 config files for the traditionnal healthcheck tests.
But I am facing some issues
I solved the first trivial ones
- needs to add demo/vFW/* files (found on demo repository)
- needs to add tobot/assetys/template/asdc/*.template
Question 1: where is the repo referencing asdc/*.template files, I did not find
it neither in testsuite nor in demo
once the configurations are added, the test is initiated but I got almost
immediately a 417 (when launching directly the test takes 1-2 minutes)
2019-03-26 10:02:29,593 - xtesting.core.robotframework - INFO -
Health Distribution Test | FAIL |
417 != 200
I put the robot logs in copy.
I assume additional stuff is missing in my docker (136 Mo).
Q2: based on the log, do you see what could be missing? env, var, lib, config
files?
Thanks & regards
Morgan
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16361): https://lists.onap.org/g/onap-discuss/message/16361
Mute This Topic: https://lists.onap.org/mt/30781186/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
