action #130778
Updated by tinita 11 months ago
## Observation Sometimes `openqa-clone-job` fails with the following error and exit code coe 255: ``` Jun 13 10:44:26 openqa openqa-gru[1676]: openqa-clone-job (62 /opt/os-autoinst-scripts/openqa-investigate): (openqa-clone-job --json-output --skip-chained-deps --max-depth 0 --parental-inheritance --within-instance https://openqa.suse.de/tests/11282276 TEST+=:investigate:last_good_build:20230608-1 _TRIGGER_JOB_DONE_HOOK=1 _GROUP_ID=0 BUILD= OPENQA_INVESTIGATE_ORIGIN=https://openqa.suse.de/t11326981) stderr: >>>Current job 11282276 will fail, because the repositories for the below updates are unavailable<<< Jun 13 10:44:26 openqa openqa-gru[1676]: openqa-clone-job (62 /opt/os-autoinst-scripts/openqa-investigate): (openqa-clone-job --json-output --skip-chained-deps --max-depth 0 --parental-inheritance --within-instance https://openqa.suse.de/tests/11282276 TEST+=:investigate:last_good_build:20230608-1 _TRIGGER_JOB_DONE_HOOK=1 _GROUP_ID=0 BUILD= OPENQA_INVESTIGATE_ORIGIN=https://openqa.suse.de/t11326981) rc: 255 >>><<< ``` It means that the cloned job would fail, so it skips cloning and returns 255. Currently the hook script will abort and be marked as a failure. Instead we should probably just accept that this job can't be cloned, but try to clone the rest and correctly finish the investigation handling in the script. ## Acceptance criteria * **AC1:** If an investigation job can't be created for the above reason, the hook script should not be marked as a failure ## Suggestions * Alternatively use a zero exit code in openqa-clone-job in those cases