[LU-15823] Maloo DB test result upload from external doesn't work

• Status: Resolved
• Project: Lustre
• Type: Bug
• Priority: Minor
• Reporter: Xinliang Liu
• Assignee: Lee Ochoa
• Resolution: Fixed
• Labels: malooDB
• Severity: 3

Description

Tried to upload test results to Maloo DB with my own account several times following the guide https://wiki.whamcloud.com/display/TEI/Test+results+format.
Either with maloo_upload.sh or through the website https://testing.whamcloud.com/import_tasks/new. But can't see any upload in the upload queue 
https://testing.whamcloud.com/import_tasks?user_id=b8340029-197d-4ce0-a8f1-40f76d3bb8c7.

Comments

[Minh Diep]

leonel8a, could you take a look?

[Lee Ochoa]

xinliang, could you please attach here the results tarball so I can investigate? Thanks.

[Xinliang Liu]

upload-liuxl.tar.gz  Here is the tar file downloaded from here and change 

'cumulative_result_id' and 'session_group_id' to different UUIDs.

[Lee Ochoa]

Hmm, not sure what issue you were having, I uploaded the tarball using https://testing.whamcloud.com/import_tasks/new, you can find it here https://testing.whamcloud.com/test_sessions/69b2f7d4-cf36-11ec-881a-07ebe308fd35 or by going to the import queue, of course this time under my name https://testing.whamcloud.com/import_tasks?user_id=5b41a8e0-84b5-11e4-b2c6-5254006e85c2.

[Xinliang Liu]

Hi Lee, thank you for your verifying.

The new attached tar file upload-for-test.tar.gzwhich delete 'cumulative_result_id' and 'session_group_id'  should be uploadable every time.

This time I can upload it by using https://testing.whamcloud.com/import_tasks/new.. I can see it in upload queue now: https://testing.whamcloud.com/import_tasks?user_id=b8340029-197d-4ce0-a8f1-40f76d3bb8c7

And I can upload it with below cmd too. The maloo_upload.sh script is downloaded from https://testing.whamcloud.com/import_tasks/new.

 ./maloo_upload.sh upload-for-test.tar.gz

But when I extract it to test-result-dir, I can not upload it successfully with below cmd.

./maloo_upload.sh test-result-dir

I found a bug on maloo_upload.sh, I can fix it with bellow change.

-  tar cfz upload.tar.gz * | curl -F "user_id=${MALOO_USER_ID}" -F "upload=@upload.tar.gz" \
+  tar cfz upload.tar.gz * && curl -F "user_id=${MALOO_USER_ID}" -F "upload=@upload.tar.gz" \ 

[Lee Ochoa]

Ah yes, thank you for noticing, I'll fix that.

[Xinliang Liu]

Just FYI,

I found that if the submission date of results.yml is too old then the result tar ball can't be uploaded.

This can explain why I can't upload previous old test results.

[Xinliang Liu]

Hi leonel8a, another issue I found is that only Maloo defined job name can be display on https://testing.whamcloud.com/test_sessions.  For example, for the upload-for-test.tar.gz test result, if I change the triggering_job_name: lustre-reviews to "lustre-reviews-1" in file results.yml, although the test result tar ball can be uploaded successfully but it can't  be display on https://testing.whamcloud.com/test_sessions.

This makes me can't set my own job name.

[Lee Ochoa]

Hi xinliang, I'm not sure the above is correct. I found all of the tarballs you uploaded by simply filtering on your name, see the screenshot in the attachments above.

Note that to prevent an explosion of job names and test groups we probably want to limit the amount of names used, I can help consolidate these if you want all the results under a certain job name and/or test group

EDIT: Actually, for job you should probably use "custom", and for test group we can probably create one that is specific to you, let me know what you'd like to call it and I can change all the existing results, if you need more than one that's ok too, that way you can split your results into different test groups, just let me know what you'd like them to be

[Xinliang Liu]

Hi leonel8a, thank you for your clarifying.

I've tried the job name "custom", it doesn't work. If possible, please help to create an job name "linaro-lustre-daily-master".

And regarding to the test group names, as you can see in the screen shot, it doesn't has any limitation, I can use my own defined names, right?

[Lee Ochoa]

I've used "custom" in the past without issues, just tried to import a copied tarball in my dev environment, changed the sessions group id and trigger job name to "custom" and it worked fine. Having said that, yes you can use "linaro-lustre-daily-master" if you'd like, the first imported set of results will create the job if it not there so feel free to go ahead, and regarding test group names also feel free to create your own they'll also be added if missing, but please keep the list short, we definitely don't want to create dozens of these.

Just occurred to me, are you by any chance looking for your results in the "EXASCALER" project? That might explain why you are not seeing them, they're saved in the "LUSTRE" project (see screenshot above)

I'd like to remove all of the test_xxx groups that were created as this is a production system, what can I rename them to? So far you've added

test-xx-01

test-xx-02

test-xx-03

xx-01

xx-02

xx-03

xxx

[Xinliang Liu]

Thank you for your help Lee, please removed those test group names. I will try my best to make the group name list short. Thanks again.

I can't see the "EXASCALER"  project, it says

"Access to project EXASCALER is restricted"

[Xinliang Liu]

Hi leonel8a,  can we just reuse job name "lustre-master" and group names "full-dne-part-1/2/3" ? Like: https://testing.whamcloud.com/test_sessions?jobs=lustre-master&user_id=b8340029-197d-4ce0-a8f1-40f76d3bb8c7&builds=104#redirect

Or use distinguishable names？

[Lee Ochoa]

You really don't want to use an existing name for a job and test group that doesn't run those exact same tests because at that point you're mixing results that are not related. And since you're running tests unrelated from the normal autotest pipeline I would definitely suggest you use your own custom distinguishable test group names and job name "custom"

[Xinliang Liu]

OK, understand I will change group names to "linaro-full-part-1/2/3".

But job name "custom" doen't works for me, I can't see my test session with job name "custom".

[Lee Ochoa]

They're right here https://testing.whamcloud.com/test_sessions?horizon=518400&jobs%5B%5D=custom&test_groups%5B%5D=linaro-full-part-1&test_groups%5B%5D=linaro-full-part-2&test_groups%5B%5D=linaro-full-part-3&source=test_sessions#redirect

[Lee Ochoa]

xinliang please remember to set the trigger_job attribute in the results file as "custom", looks like you've uploaded results with "lustre-master" as the job in the last few days, this generated some errors on the maloo side because other properties are missing which are required for non-custom jobs

 

https://testing.whamcloud.com/test_sessions?jobs%5B%5D=lustre-master&user_id=b8340029-197d-4ce0-a8f1-40f76d3bb8c7&start_date=2022-05-29&end_date=2022-06-01&source=test_sessions#redirect

[Xinliang Liu]

OK, I stop uploading results with job name "lustre-master" now.

Again, I can't see any record in the links: https://testing.whamcloud.com/test_sessions?horizon=518400&jobs%5B%5D=custom&test_groups%5B%5D=linaro-full-part-1&test_groups%5B%5D=linaro-full-part-2&test_groups%5B%5D=linaro-full-part-3&source=test_sessions#redirect or https://testing.whamcloud.com/test_sessions?jobs=custom&user_id=b8340029-197d-4ce0-a8f1-40f76d3bb8c7#redirect

I have uploaded two tarball with the job name "custom" today.

This job name doesn't work for me. Please help to check it.

 

[Lee Ochoa]

I see what is happening, you should be able to see all your uploads now, any new ones will not show until I get a fix in place, maybe tomorrow or early next week at the latest. Sorry for the inconvenience.

[Xinliang Liu]

Hi Lee, I can see the new upload test sessions with group name "custom" now. Thanks a lot.