QA (public) » openQA Project (public)

Hi, could you please share the URLs to the actual jobs in a reachable openQA instance for reference? I assume this is coming from openqa.suse.de . This could help to understand properly what is going on.

Julie_CAO wrote:

Given a common scenario in our daily test, a test(the red one in the middle of the graph A) in a job chain fails .

1. We give a glimpse of the failing test and it does not look like a product issue( pxe/ipmi/needle_mismatch/network_glitch/openqa or other environment issue).

In the above example the job shows up as "incomplete" but that shouldn't matter for the rest of the observation you describe.

The only feasible way I know so far is with the command line(/usr/share/openqa/script/client isos post ...), but it needs extra permission(admin permission?)

The further down described restarting/retriggering is likely the better way but in case for using the openQA-client at least a better start is with openqa-cli api -X post … instead of the full-path of /usr/share/openqa/…

[…]

1. Finally, we'd like rerun the entire job chain to test product again […] But it is no way via web UI

You should be able to just retrigger the original parent, "install_15sp4_xen_host@64…" in your example. If you only want to retrigger failed jobs in the dependency tree then you can do that with the skip_ok_result_children=1 API parameter as described in http://open.qa/docs/#_handling_of_related_jobs_on_failure_cancellation_restart . So you could use e.g. openqa-cli api --osd -X post jobs/<job_id>/restart skip_ok_result_children=1. With https://github.com/os-autoinst/openQA/pull/4417 this should also be possible over the webUI

Julie_CAO wrote:

1. Finally, we'd like rerun the entire job chain to test product again […] But it is no way via web UI

You should be able to just retrigger the original parent, "install_15sp4_xen_host@64…" in your example. If you only want to retrigger failed jobs in the dependency tree then you can do that with the skip_ok_result_children=1 API parameter as described in http://open.qa/docs/#_handling_of_related_jobs_on_failure_cancellation_restart . So you could use e.g. openqa-cli api --osd -X post jobs/<job_id>/restart skip_ok_result_children=1. With https://github.com/os-autoinst/openQA/pull/4417 this should also be possible over the webUI

I can handle step 2 to rerun only failing jobs, but my problem is step 4: after part of tests in the chain has been retriggered, the original ones(those have not been triggered) are unable to be restarted any more, because their parant job has been cloned already.

so do I understand correctly that you would like to retrigger the complete chain after parts of it have been initially retriggered? In any case I guess this would then actually be a new feature so putting to "future" for now