Actions
action #175485
closedcoordination #102906: [saga][epic] Increased stability of tests with less "known failures", known incompletes handled automatically within openQA
coordination #175515: [epic] incomplete jobs with "Failed to find an available port: Address already in use"
jobs incomplete with auto_review:"setup failure: isotovideo can not be started" - why did osd-deployment trigger even though openQA-in-openQA as already showing incompletes? size:S
Start date:
2025-01-15
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Observation¶
We have a check in the GitLab pipeline to evaluate the openQA in openQA test state. Seemingly the pipeline was fine even though we know things failed in production as reported in #175464.
Acceptance critiera¶
- AC1: The OSD deployment is not executed when openQA-in-openQA tests fail
Suggestions¶
- The check in bash is obviously wrong
- The sleep probably overrides the return code?
- Consider splitting the lines or move this to a proper script https://gitlab.suse.de/openqa/osd-deployment/-/blob/ebf5bcdc339b4aee17933f99aa89217f329da386/.gitlab-ci.yml#L160
- The check was exhausting the retries when it ran on 2025-01-15 and wrongfully passed.
Rollback actions¶
- DONE enable notification emails again in https://gitlab.suse.de/openqa/osd-deployment/-/settings/integrations/pipelines_email/edit
Actions